- From: <bugzilla@jessica.w3.org>
- Date: Mon, 19 Mar 2012 19:02:21 +0000
- To: www-dom@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16333
Travis Leithead [MSFT] <travil@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #7 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-03-19 19:02:19 UTC ---
(In reply to comment #6)
> Was it not decided that InvalidCharacterError could never be thrown for
> Event.type? That Event.type could be anything.
I don't see InvalidCharacterError being thrown in DOM4.
I also tested the major browsers to see if any threw a similar error, of those
tested (Opera, IE, Chrome, Safari, Firefox), none of them threw this error (or
an error by its former name). I tried with random unicode characters, spaces,
null/"null" (which is still inconsistent between browsers), and embedded nulls.
Given these test results, I will be removing the criteria for this exception.
(I also don't see NotSupportedError being thrown from DOM4 either, though this
test appears to pass in all major browsers:
http://samples.msdn.microsoft.com/ietestcenter/domevents/domevents_harness.htm?url=createEvent.NOT_SUPPORTED_ERR.html)
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 19 March 2012 19:02:23 UTC