Closed
Bug 845262
Opened 13 years ago
Closed 7 years ago
loadstart event not dispatched by video element
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: niels, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.56 Safari/537.17
Steps to reproduce:
1. Load URL: http://html5test.com/t/video/9ff.html
2. Look at area below the video element
There are handlers bound to many of the events dispatched by the video element. These handlers print something below the video element.
If the loadstart event is dispatched, it should print "Loading...".
Actual results:
The loadstart event is never dispatched.
Expected results:
The spec says the loadstart event should be dispatched when "The user agent begins looking for media data, as part of the resource selection algorithm."
All Trident and WebKit based browsers do dispatch this event.
Comment 1•13 years ago
|
||
The test attaches the listeners from script in the body of the document after the video element is declared with sources. It's possible (and, I believe, valid) for the video element to start loading before the script runs, and thus for any events that fire before the event listeners are registered to be missed by the script.
The first time I ran the test in Chrome, I didn't see "Loading..." printed, so this race also occurs in other browsers. I think the test needs to be altered to register for the events it's interested in before they could fire.
Updated•10 years ago
|
Component: Audio/Video → Audio/Video: Playback
Comment 2•7 years ago
|
||
Mass closing because of inactivity.
Please feel free to re-open if still relevant.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•