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 9205 - I'm missing a specification on the relation between onreadystatechange and onload. Will they be used interchangeably? When will they fire? Will onreadystatechange fire multiple times during downloading an external resource (readystate="loading")?
Summary: I'm missing a specification on the relation between onreadystatechange and on...
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: LC
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-03-06 21:23 UTC by contributor
Modified: 2010-10-04 13:59 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-03-06 21:23:49 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#event-handlers-on-elements,-document-objects,-and-window-objects

Comment:
I'm missing a specification on the relation between onreadystatechange and
onload. Will they be used interchangeably? When will they fire? Will
onreadystatechange fire multiple times during downloading an external resource
(readystate="loading")?

Posted from: 93.206.147.106
Comment 1 Ian 'Hixie' Hickson 2010-03-30 22:20:54 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: Rejected
Change Description: no spec change
Rationale: This is defined in great detail here:
   http://www.whatwg.org/specs/web-apps/current-work/multipage/the-end.html#the-end
Comment 2 Axel Dahmen 2010-04-01 09:18:34 UTC 
Thanks for enlightening me.

Is this sequence also true then for external resources? As far as I can see, the description seems to only describe the process of loading HTML documents. It doesn't seem to decribe the sequence of events happening when external resouces are interactively loaded (e.g. images, scripts, style sheets) by means of DOM manipulation.
Comment 3 Ian 'Hixie' Hickson 2010-04-12 07:23:54 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: The processing for those is defined in the sections that define how those work. I'm not sure what could be done to make the spec clearer.
Comment 4 Axel Dahmen 2010-05-07 03:26:22 UTC 
Agreed. The HTML5 spec has become quite huge. It's hard to find things in there. The corresponding events are missing cross-references to the mentioned topic.

Perhaps a reorganization might feel appropriate?