1032246 - Media elements should not trigger events for control interactions

Status: NEW

(Toolkit :: Video/Audio Controls, defect)

Description

[Chris Adams]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36

Steps to reproduce:

1. Open http://www.quirksmode.org/html5/tests/video.html

2. Run the following JavaScript in the console:

Array.prototype.forEach.call(document.querySelectorAll('video'), function (i) {
    i.parentNode.addEventListener('mousedown', function (evt) { console.log(evt.type) });
    i.parentNode.addEventListener('mouseup', function (evt) { console.log(evt.type) });
    i.parentNode.addEventListener('click', function (evt) { console.log(evt.type) });
})

3. Click on the play/pause button on a <video> element with native controls



Actual results:

The mousedown, mouseup and click events are triggered on the video element and the event data does not include a way to distinguish between a click on the video itself or a control interaction


Expected results:

According to the HTML specification, native controls on the media element should not trigger normal mouse
events:

“If the user agent exposes a user interface to the user by displaying controls over the media element, then
the user agent should suppress any user interaction events while the user agent is interacting with this
interface. (For example, if the user clicks on a video's playback control, mousedown events and so forth
would not simultaneously be fired at elements on the page.)”

http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#attr-media-controls

Comment 1

[[:Aleksej]]

Related: bug 582537?

Comment 2

[Chris Adams]

This was recently fixed in Chrome: https://code.google.com/p/chromium/issues/detail?id=269454

Comment 6

[ccd0]

Another apparent consequence of this bug is that when a video element is inside a link, the controls on the video can't be readily operated without navigating to the linked page.  For example

http://regex.info/exif.cgi?imgurl=https://a.pomf.cat/tyyvie.webm

This can be very annoying.

Comment 7

[Jonathan Watt [:jwatt]]

Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)