W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: ISSUE-118 (dispatchEvent links): Consider allowing dispatchEvent for generic event duplication for links [DOM3 Events]

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 21 Jul 2010 17:07:42 -0700
Message-ID: <AANLkTin7XtuZslO1HBJl-CG-Mp1fYbrTXjb6FHLj9n4L@mail.gmail.com>
To: Web Applications Working Group WG <public-webapps@w3.org>
On Wed, Jul 21, 2010 at 10:11 AM, Web Applications Working Group Issue
Tracker <sysbot+tracker@w3.org> wrote:
>
> ISSUE-118 (dispatchEvent links): Consider allowing dispatchEvent for generic event duplication for links [DOM3 Events]
>
> http://www.w3.org/2008/webapps/track/issues/118
>
> Raised by: Doug Schepers
> On product: DOM3 Events
>
> Simon Pieters wrote in <http://lists.w3.org/Archives/Public/www-dom/2010AprJun/0041.html> :
> [[
> Is it defined what should happen in the following case?
>
> <div onclick="document.links[0].dispatchEvent(event)">click me</div>
> <a href="http://example.org/">test</a>
>
> It seems Firefox and Opera throw an exception, while WebKit allows the event to be dispatched.
>
> I think it seems like a neat thing to be able to do, for making table rows or <canvas> clickable. (However the event shouldn't be a 'trusted' event in that case, of course.) To make it work today you'd have to create a new event and copy over all properties, which is annoying.
> ]]

Even if we make this dispatch the event, it wouldn't make the link be
followed — since the event isn't dispatched by the UA, there's no
default action. There is, in any case, a simpler solution to the
above:

 <div onclick="document.links[0].click()">click me</div>
 <a href="http://example.org/">test</a>

-- 
Ian Hickson
Received on Thursday, 22 July 2010 00:08:14 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:40 GMT