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 12764 - onerror discrepencies
Summary: onerror discrepencies
Status: RESOLVED INVALID
Alias: None
Product: QA
Classification: Unclassified
Component: QASpec-GL (show other bugs)
Version: unspecified
Hardware: Other All
: P3 normal
Target Milestone: ---
Assignee: Karl Dubost
QA Contact: Karl Dubost
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-25 06:45 UTC by Michael[tm] Smith
Modified: 2011-05-25 06:46 UTC (History)
0 users

See Also:


Attachments

Description Michael[tm] Smith 2011-05-25 06:45:31 UTC
Comment from: Patrick Mueller <pmuellr@gmail.com>
http://www.w3.org/mid/BANLkTimFxigM8N2OhzEcEH5Ao74Kqq+50Q@mail.gmail.com

I was looking over the onerror bits in
http://dev.w3.org/html5/spec/Overview.html , and noticed that the
sections #event-handler-attributes (6.1.6.1) and #runtime-script-errors
(6.1.3.5) seem to differ:

#event-handler-attributes

* 1st argument is "event"
* 3rd argument is "fileno"

#runtime-script-errors

* 1st argument is a DOMString message
* 3rd argument is a line number

I assume the intention is that the 3rd argument should be a line number and
not "file number" (fileno).  But should it be a DOMString?  Why not a number
type?

For the first argument, calling the argument an "event" (in
#event-handler-attributes)
would kinda indicate to me that it's an event object, not a message.

Perhaps these two sections are talking about different things, which would
be even more confusing, since "onerror" seems to be a bit of a weird beast
in any case.

-- 
Patrick Mueller
http://muellerware.org