This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html Multipage: http://www.whatwg.org/C#read-image Complete: http://www.whatwg.org/c#read-image Comment: Should define page load processing model for video/audio Posted from: 91.181.252.157 User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.35 (KHTML, like Gecko) Chrome/13.0.761.0 Safari/534.35
It it defined, by the resource selection algorithm, resource fetch algorithm and the delaying-the-load-event flag.
Not sure if we're talking about the same thing; this bug is about the DOM in <iframe src=video></iframe>
OK, in that case it needs to be updated with the details about what should be defined.
"Copy http://www.whatwg.org/C#read-image; s/img/video/."
Just copying the section won't help, since nothing would invoke the section. :-P Do browsers actually all do this natively these days or do they still just invoke a plugin?
Gecko does, at least.
(In reply to comment #5) > Do browsers actually all do this natively these days or do they still just > invoke a plugin? Opera creates a dummy HTML document with a <video> element in it.
(In reply to comment #7) > (In reply to comment #5) > > Do browsers actually all do this natively these days or do they still just > > invoke a plugin? > > Opera creates a dummy HTML document with a <video> element in it. ...and a dummy HTML document with an <audio> element in it for supported audio/* types.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r6630. Check-in comment: Define navigating to video and audio resources http://html5.org/tools/web-apps-tracker?from=6629&to=6630
Looks good, thanks