Re: DOMActivate vs. Click

On Jul 26, 2009, at 2:52 PM, Jonas Sicking wrote:

> On Sun, Jul 26, 2009 at 4:36 AM, Anne van Kesteren<annevk@opera.com>  
> wrote:
>> On Sun, 26 Jul 2009 07:55:10 +0200, Jonas Sicking  
>> <jonas@sicking.cc> wrote:
>>> On Wed, Jul 22, 2009 at 9:35 AM, Anne van Kesteren<annevk@opera.com>
>>> wrote:
>>>> I'd be very happy if could consider yet again dropping
>>>> DOMFocusIn/DOMFocusOut/DOMActivate.
>>>
>>> What do you mean by "dropping"? Dropping from the DOM Events L3  
>>> spec,
>>> or dropped from the web platform entirely? Including dropped from  
>>> SVG?
>>
>> From the Web platform.
>>
>>
>>> Would Opera be willing to completely remove support for these  
>>> events?
>>> I'd personally love to remove them entirely from gecko, just not  
>>> sure
>>> if any existing content would break.
>>
>> Well, we do not support DOMActivate to begin with. DOMFocusIn and  
>> DOMFocusOut would require a bit more careful investigation, but I'm  
>> pretty sure we'd be willing to try.
>
> Sounds great, I'm all for this too. cc'ing some gecko folks that might
> have an opinion.

For what it's worth, in WebKit we support these events (DOMActive,  
DOMFocusIn and DOMFocusOut) solely for reasons of spec compliance and  
compatibility with other engines. If we determine that they are not  
necessary for compatibility with existing content,  they end up  
dropped from the relevant specs, and other engines remove (or refrain  
from adding) support, then we'd probably remove them as well. I can't  
speak definitively for the whole project but that is my sense of most  
people's thinking.

Regards,
Maciej