- From: <bugzilla@jessica.w3.org>
- Date: Sun, 10 Mar 2013 04:23:13 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18515 --- Comment #3 from David Dorwin <ddorwin@google.com> --- The stalled event [1] is related to resource fetching [2] and not necessarily the next frame being available. When _data_ for the next frame is not available, it is a blocked media element [3]. That still doesn't address the case where the data is available but is not ready for rendering in time (i.e. has not been decoded). The lack of a frame for rendering because it can't be decrypted is closer to not having a frame from the decoder, though it could persist for longer periods. The HTML5 spec doesn't appear to address the case when data or frames for one stream is available and another is not for the same media element. [1] http://www.w3.org/TR/2012/CR-html5-20121217/embedded-content-0.html#event-media-stalled [2] http://www.w3.org/TR/2012/CR-html5-20121217/embedded-content-0.html#stall-timeout [3] http://www.w3.org/TR/2012/CR-html5-20121217/embedded-content-0.html#blocked-media-element -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 10 March 2013 04:23:14 UTC