- From: <bugzilla@jessica.w3.org>
- Date: Wed, 26 Oct 2011 23:55:00 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14175
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ap@webkit.org,
| |jonas@sicking.cc,
| |w3c@adambarth.com
--- Comment #7 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-10-26 23:54:59 UTC ---
Looks like no: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1236
Seems like Firefox sets it lazily and finds the error the first time it's
fetched, whether for execution or because it's being serialised; it then fires
onerror (but doesn't throw an exception) and sets it to null.
IE fires onerror as soon as the attribute is parsed by the HTML parser, and
treats the attribute as being null afterwards.
Chrome tries to compile it every time it's accessed, and throws an exception
each time (leading to onerror if it's not caught).
(Safari and Opera don't seem to support onerror.)
--
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 Wednesday, 26 October 2011 23:55:01 UTC