Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 302279 "Traditional model" for registrating DOM events doesn't work on media events
Starred by 4 users Project Member Reported by henr...@opera.com, Oct 1 2013 Back to list
Status: Fixed
Owner:
Email to this user bounced
Closed: Oct 2013
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Blocked on:
issue 305112



Sign in to add a comment
UserAgent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.13

Example URL:
http://people.opera.com/henriks/video-events.html

Steps to reproduce the problem:
1. Open http://people.opera.com/henriks/video-events.html
2. Hit play on the video controls

What is the expected behavior?
An alert message should appear, indicating that a play event was fired.

What went wrong?
The play event is not fired when being registered using:
elm.onplay = onplay;

Using addEventListener works, however, and so does inline event handling.

Did this work before? N/A 

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes Internet Explorer 11.0.9431.0 and Opera 12.13

Chrome version: 31.0.1650.0 dev  Channel: dev
OS Version: Fedora 18
Flash Version: 

Looking at <http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#event-handlers-on-elements,-document-objects,-and-window-objects>, this seems to be a problem on all "media related events", e.g.: oncanplay, onloadedmetadata, onpause, onvolumechange, &c.

I'm not sure if this has been working in the past, but I've reproduced it in 29.0.1547.76 as well.
 
Comment 1 by phil...@opera.com, Oct 1 2013
Cc: aaron@chromium.org
Aaron, I presume that you know about this? Are patches welcome, or is this intentionally not supported?
Cc: -aaron@chromium.org acolwell@chromium.org
Hmm.. I'm amazed we don't have tests that verify this behaior. Patches are definitely welcome.
Comment 3 by tkent@chromium.org, Oct 2 2013
Labels: Hotlist-GoodFirstBug Cr-Blink-Video
Comment 4 by phil...@opera.com, Oct 2 2013
Status: Untriaged
Some digging reveals that these properties have been explicitly excluded since at least <https://trac.webkit.org/changeset/44928>. That change doesn't remove any previous code involving onplay or similar, so presumably the properties weren't implemented before that either.
Comment 5 by phil...@opera.com, Oct 2 2013
Somewhat surprisingly, the media-related event properties have been on Window since <https://trac.webkit.org/changeset/44302>. That's per spec, but serves no real purpose as opposed to the properties on Element...
Comment 6 by phil...@opera.com, Oct 2 2013
Since it looks like this isn't just an oversight and possibly intentional, I'll consult with blink-dev before going further. I have a trivial patch to enable the properties, but perhaps there's some history here I need to know.
Comment 7 by phil...@opera.com, Oct 10 2013
Blockedon: chromium:305112
Comment 8 by phil...@opera.com, Oct 17 2013
Owner: phil...@opera.com
Status: Fixed
This was fixed as part of  issue 305112 , in Blink r159781.
Comment 9 by sshru...@google.com, Mar 21 2016
Components: -Blink>Video Blink>Media>Video
Renaming Blink>Video to Blink>Media>Video for better characterization
Sign in to add a comment