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.
Starred by 4 users
Status: Fixed
Email to this user bounced
Closed: Oct 2013
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Blocked on:
issue 305112

Sign in to add a comment
"Traditional model" for registrating DOM events doesn't work on media events
Project Member Reported by, Oct 1 2013 Back to list
UserAgent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.13

Example URL:

Steps to reproduce the problem:
1. Open
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 <,-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, Oct 1 2013
Aaron, I presume that you know about this? Are patches welcome, or is this intentionally not supported?
Hmm.. I'm amazed we don't have tests that verify this behaior. Patches are definitely welcome.
Comment 3 by, Oct 2 2013
Labels: Hotlist-GoodFirstBug Cr-Blink-Video
Comment 4 by, Oct 2 2013
Status: Untriaged
Some digging reveals that these properties have been explicitly excluded since at least <>. 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, Oct 2 2013
Somewhat surprisingly, the media-related event properties have been on Window since <>. That's per spec, but serves no real purpose as opposed to the properties on Element...
Comment 6 by, 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, Oct 10 2013
Blockedon: chromium:305112
Comment 8 by, Oct 17 2013
Status: Fixed
This was fixed as part of  issue 305112 , in Blink r159781.
Comment 9 by, 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