W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2013

Re: [whatwg] Should <video controls> generate click events?

From: Philip Jägenstedt <philipj@opera.com>
Date: Wed, 11 Sep 2013 10:51:44 +0200
Message-ID: <CAMQvoC=Na_25VMzLeY=fWhtQ1Ot-mPPhy5G=4stCfJaUcGDdMw@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: WHAT Working Group <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>
On Wed, Sep 11, 2013 at 10:48 AM, Simon Pieters <simonp@opera.com> wrote:
> On Wed, 11 Sep 2013 01:35:00 +0200, Ian Hickson <ian@hixie.ch> wrote:
>> On Wed, 21 Aug 2013, Robert O'Callahan wrote:
>>> I think you basically have to assume that if you specify "controls" then
>>> the controls may accept clicks anywhere in the video element. There's
>>> nothing in the spec to say that the controls must be restricted to a bar
>>> of a certain height at the bottom of the element.
>> 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.

What does "visible" mean here, is it to handle cases where the UA
force-enables the controls without adding the controls attribute to
the DOM?

Received on Wednesday, 11 September 2013 08:52:13 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:09 UTC