W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2010

Re: DOM3 Events last call comment

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Thu, 21 Oct 2010 15:09:47 -0700
Message-ID: <AANLkTin_nbgBWbq-2bGqV01XTaUk0KcY4e2pma1k4cuM@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>, Steven Pemberton <Steven.Pemberton@cwi.nl>, Jonas Sicking <jonas@sicking.cc>
Cc: www-dom@w3.org
On 10/21/10, Simon Pieters <simonp@opera.com> wrote:
> On Thu, 21 Oct 2010 05:19:54 +0200, Jonas Sicking <jonas@sicking.cc> wrote:
>
>> On Mon, Oct 18, 2010 at 5:23 AM, Steven Pemberton
>> <Steven.Pemberton@cwi.nl> wrote:
[...]

>
> Nuke DOMActivate from orbit and replace it with click.
>

A Reagan-era Star Wars approach to API misfeatures.

> Also see http://www.w3.org/Bugs/Public/show_bug.cgi?id=10899
>
>
The comments there show that DOMActivate is not interoperable.

But they don't show why it failed. Is it worth taking a look at that,
as a failed feature postmortem? Seems DOMActivate had merits but with
no way to feature test it, poor interop, and an alternative "click",
it was dead in the water.

New features should be feature testable and events should be, too.

About Steve Pemberton's other point:

"Another problem is that if true hardware events, like click, get
mixed up with the abstract events like DOMActivate, then it will be
harder to differentiate between hardware events when you need them,
and abstract events when you don't."

If the program cares about activation then it should listen for
"click". But for touchscreen hardware, does a "touch" cause a "click"
event to fire in all browsers?

Garrett
Received on Thursday, 21 October 2010 22:10:24 GMT

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