- From: <bugzilla@jessica.w3.org>
- Date: Mon, 12 Mar 2012 20:56:05 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16333 --- Comment #3 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-03-12 20:56:04 UTC --- [see http://lists.w3.org/Archives/Public/www-dom/2011JanMar/0093.html] From: Jacob Rossi <jrossi@microsoft.com> Date: Thu, 10 Mar 2011 23:04:11 +0000 Yes. Looks like IE9 throws it for the scenario I described (redispatching a trusted event) and also when you call createEvent( ) with an unrecognized interface, like createEvent("foo"). > -----Original Message----- > From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU] > Sent: Wednesday, March 09, 2011 7:38 PM > To: Anne van Kesteren > Cc: www-dom@w3.org; Jacob Rossi > Subject: Re: [DOM3Events] Exceptions > > On 3/9/11 1:35 PM, Anne van Kesteren wrote: > > On Wed, 09 Mar 2011 19:04:23 +0100, Jacob Rossi <jrossi@microsoft.com> > > wrote: > >> IE9 also throws NOT_SUPPORTED_ERR (per the spec). > > > > I think what Boris and Ojan said is that WebKit and Gecko sometimes > > throw NOT_SUPPORTED_ERR. Not whether they throw it for dispatchEvent() > > and so far nobody has given an example of when dispatchEvent() would > > throw that (in actual code). > > Oh, I was missing that context. dispatchEvent does not throw > NOT_SUPPORTED_ERR in Gecko. The only event-related thing that seems to is > createEvent. > > Trying to redispatch a trusted event will reset it to untrusted, then allow > redispatch in Gecko. > > -Boris > -- Configure bugmail: https://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 Monday, 12 March 2012 20:56:07 UTC