This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9800 - The wording for the suspend event ("but does not have the entire media resource downloaded") puts it in the same boat as the removed load event. The description should reflect that the event is fired when the networkState changes to the state of NETWORK_I
Summary: The wording for the suspend event ("but does not have the entire media resour...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-22 21:19 UTC by contributor
Modified: 2010-10-04 14:45 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-05-22 21:19:24 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#mediaevents

Comment:
The wording for the suspend event ("but does not have the entire media
resource downloaded") puts it in the same boat as the removed load event. The
description should reflect that the event is fired when the networkState
changes to the state of NETWORK_IDLE, which can happen if the media finishes
downloading.

Posted from: 174.25.216.69
Comment 1 Ian 'Hixie' Hickson 2010-08-25 23:04:28 UTC 
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? We got rid of 'onload' to prevent people from waiting until the 'load' event before playing the resource, in the case where the user agent suspended the download awaiting any of it to play. Surely in the case of 'suspend' that problem doesn't exist?