IMO the high volume snap should not go away just because the video got paused. For this, indicator-sound has everything it needs in its hands. The headphones + playback + high volume should be a trigger for the dialog, not a state.
The correct workflow in this case is, IMO:
- user presses volume up
- sound indicator triggers the high volume warning without changing volume
- video gets paused, because you can't see it (at least on the phone with current design)
\ - user cancels the dialog
- volume level remains
\ - user accepts the dialog
- volume is increased
- media player gets focused
- playback should resume (?)
Whether that's universally true for all dialogs, like Matthew pointed out - maybe not. We currently have no way of discerning which dialog should cause that, and which should not.
IMO the high volume snap should not go away just because the video got paused. For this, indicator-sound has everything it needs in its hands. The headphones + playback + high volume should be a trigger for the dialog, not a state.
The correct workflow in this case is, IMO:
- user presses volume up
- sound indicator triggers the high volume warning without changing volume
- video gets paused, because you can't see it (at least on the phone with current design)
\ - user cancels the dialog
- volume level remains
\ - user accepts the dialog
- volume is increased
- media player gets focused
- playback should resume (?)
Whether that's universally true for all dialogs, like Matthew pointed out - maybe not. We currently have no way of discerning which dialog should cause that, and which should not.