W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2011

RE: [DOM3Events] Exceptions

From: Jacob Rossi <jrossi@microsoft.com>
Date: Thu, 10 Mar 2011 23:04:11 +0000
To: Boris Zbarsky <bzbarsky@MIT.EDU>, Anne van Kesteren <annevk@opera.com>
CC: "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <D0BC8E77E79D9846B61A2432D1BA4EAE0276A13B@TK5EX14MBXC110.redmond.corp.microsoft.com>
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
> 

Received on Thursday, 10 March 2011 23:04:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:07 GMT