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 17940 - Well, I'm on it again. The description on events is a shambles. I'm trying to write a course on HTML 5 and the information is contradictory or missing. First, as before, the section "Global attributes" lists what it purports to be the event handler conten
Summary: Well, I'm on it again. The description on events is a shambles. I'm trying to...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 07:20 UTC by contributor
Modified: 2012-10-22 03:10 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-07-18 07:20:38 UTC 
This was was cloned from bug 16878 as part of operation convergence.
Originally filed: 2012-04-27 22:01:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2012-04-27 22:01:52 +0000 
--------------------------------------------------------------------------------
Specification: http://dev.w3.org/html5/spec/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
Well, I'm on it again. The description on events is a shambles. I'm trying to
write a course on HTML 5 and the information is contradictory or missing.

First, as before, the section "Global attributes" lists what it purports to be
the event handler content attributes that may be specified on any HTML
element. But, as mentioned before, these events are not described there.

But there are places scattered around the doc where various events are
described. What's disturbing is there are events described in these places
that are not on the list in "Global attributes" and there are events in
"Global attributes" that are not found anywhere I could see in the doc.

First, events listed in "Global attributes" that I could not find other
references for:

* oncancel
* onclose


Then events I found elsewhere that are not in the "Global attributes" list :

* addtrack
* afterprint
* beforeprint
* beforeunload
* DOMContentLoaded
* enter
* exit
* error
* message
* offline
* online
* pagehide
* pageshow
* popstate
* readystatechange



(By the way, there is a reference to framesets in "Event handlers on elements,
Document objects, and Window objects", but I thought framesets have been
removed.)


I understand this is an enormous project with tons of detail, and I appreciate
your work and effort. I'm just trying to point out some areas of concern so
you can address them when they bubble to the top of the priorty list.

Kind regards,

-Steve Comstock
steve@trainersfriend.com

Posted from: 174.29.123.115
User agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20100101 Firefox/12.0
================================================================================
Comment 1 Ian 'Hixie' Hickson 2012-07-27 05:58:39 UTC 
> First, events listed in "Global attributes" that I could not find other
> references for:
> 
> * oncancel
> * onclose

For the two places where those are mentioned, I've added <dfn> elements to make the links work.


> Then events I found elsewhere that are not in the "Global attributes" list :
> 
> * addtrack
> * afterprint
> * beforeprint
> * beforeunload
> * DOMContentLoaded
> * enter
> * exit
> * error
> * message
> * offline
> * online
> * pagehide
> * pageshow
> * popstate
> * readystatechange

There are all either on Window, <body>, or non-Node objects.


> (By the way, there is a reference to framesets in "Event handlers on elements,
> Document objects, and Window objects", but I thought framesets have been
> removed.)

They have been obsoleted, but still have to be supported.


Generally speaking, onfoo attributes aren't for specific events, they're for specific event _types_, which could be fired for any number of reasons, including random author script. So there's not necessarily a 1:1 mapping from onfoo attributes to a specific place in the spec that fires 'foo' events. I wouldn't bother looking too closely for a link here.
Comment 2 Silvia Pfeiffer 2012-10-22 03:10:24 UTC 
For completeness, was closed in r7219