[whatwg] Should <video controls> generate click events?
ian at hixie.ch
Tue Nov 26 14:46:09 PST 2013
On Tue, 10 Sep 2013, Glenn Maynard wrote:
> the activation behavior for videos should be to toggle play/pause. If
> only some browsers do it, it's an interop problem, and it seems like the
> right default behavior.
> I'm not sure whether this should only be when browser controls are
> enabled or not. It might be best to keep them orthogonal, so browser
> controls are always UI controls that don't generate click events at all.
On Wed, 11 Sep 2013, Simon Pieters wrote:
> On Wed, 11 Sep 2013 01:35:00 +0200, Ian Hickson <ian at hixie.ch> wrote:
> > True, but there _is_ something now that says that if the browser
> > considers it the user interacting with a control, that there shouldn't
> > be events sent to the page. It's either a control (no events), or an
> > activation behaviour (click events, can be canceled by
> > preventDefault()).
> Saying that Firefox's "click anywhere to play" isn't a control but
> rather activation behavior for the element makes sense. If other
> browsers want to implement that behavior, it would be good if the spec
> called out this difference.
> > Should we make this an explicit activation behaviour for the <video>
> > element if it has a controls="" attribute?
> That might be good so that the behavior is consistent between browsers.
> However, I think it should be conditional on whether the controls are
> visible rather than whether the controls attribute is present.
(As a side-effect, this means that if you put an accesskey="" attribute on
a <video> element, you can trigger the pause/play behaviour from the
keyboard, and you can use such a <video> as a master command for a
<menuitem> with a command="" attribute.)
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg