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 8230 - It might be good with a comment in script's Content attributes section mentioning onload/onerror being defined in Global attributes (I've had the question come up several times about script.onload missing from html5).
Summary: It might be good with a comment in script's Content attributes section mentio...
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: 2009-11-07 19:52 UTC by contributor
Modified: 2010-10-04 13:59 UTC (History)
4 users (show)

See Also:


Attachments

Description contributor 2009-11-07 19:52:19 UTC
Section: http://www.whatwg.org/specs/web-apps/current-work/#script

Comment:
It might be good with a comment in script's Content attributes section mentioning onload/onerror being defined in Global attributes (I've had the question come up several times about script.onload missing from html5).

Posted from: 83.227.224.93
Comment 1 Ian 'Hixie' Hickson 2010-01-05 03:08:37 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: How would this look? Which attributes should I mention for which elements? I'm concerned that this would quickly become intractable when applied consistently to the spec as a whole.