- From: <bugzilla@jessica.w3.org>
- Date: Fri, 12 Nov 2010 20:34:46 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10898
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-11-12 20:34:45 UTC ---
Interesting, Firefox does indeed do that. Weird.
Every other browser I tested (Chrome dev, which fixes the bug you mentioned;
Opera 10.x; IE8) does this the way the spec describes. Given that the behaviour
is somewhat reasonable, I think following the path of least resistance to
interop is the way to go here (i.e. go with the majority of implementations).
Note that working around this as an author is trivial - just move the
onclick="" from <body> to <html>. That already works in all the browsers I
tested (IE8, Firefox, Chrome, Opera, Safari). This isn't the case for
onload="", onblur="", etc, which is why it makes sense to have them
special-cased on <body>.
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: see above
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 12 November 2010 20:34:49 UTC