12762 2011-05-25 06:24:02 +0000 onerror discrepencies 2011-05-25 06:31:01 +0000 1 1 1 Unclassified QA QASpec-GL unspecified Other All RESOLVED INVALID P3 normal --- 1 mike karl karl oldest_to_newest 48781 0 mike 2011-05-25 06:24:02 +0000 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