12289 2011-03-11 16:37:06 +0000 <video> suspend event "Dispatched when..." is incorrect 2011-09-22 17:42:41 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#mediaevents P3 normal --- 12595 1 contributor ian ian mike philipj public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 46631 0 contributor 2011-03-11 16:37:06 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html Section: http://www.whatwg.org/specs/web-apps/current-work/#mediaevents Comment: suspend event "Dispatched when..." is incorrect Posted from: 83.218.67.122 User agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.8.115 Version/11.10 46632 1 philipj 2011-03-11 16:39:22 +0000 The description is "The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded.", but the resource fetch algorithm also fires the suspend event "Once the entire media resource has been fetched (but potentially before any of it has been decoded)". In other words, the UA may have the entire resource downloaded when the last buffered event is fired. 49564 2 ian 2011-06-14 07:41:01 +0000 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: Did Not Understand Request Change Description: no spec change Rationale: I don't understand. Could you elaborate? As far as I can tell in the spec, 'suspend' is only fired in one situation, which is when the download is suspended. I guess technically a browser could decide to not download any more content at the same time as it has received the last byte but before realising it, but that's a pretty obscure edge case that doesn't seem worth mentioning in the non-normative summary table. 49574 3 philipj 2011-06-14 09:58:45 +0000 This bug should be considered together with Bug 12595. After making the suspend event fire when even if we've finished buffering, the wording can be changed to simply "The user agent is intentionally not currently fetching media data" 53032 4 mike 2011-08-04 05:06:09 +0000 mass-moved component to LC1 57106 5 ian 2011-09-21 20:42:59 +0000 This should indeed be changed now. 57165 6 ian 2011-09-22 17:40:22 +0000 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: Agreed with comment 3. 57166 7 contributor 2011-09-22 17:42:41 +0000 Checked in as WHATWG revision r6561. Check-in comment: 'suspend' event's description was out of date http://html5.org/tools/web-apps-tracker?from=6560&to=6561