Re: DOMActivate vs. Click

Hi, Folks-

Can someone please enlighten me why removing DOMFocusIn, DOMFocusOut, 
and DOMActivate from existing implementations seems like a good idea?

I suppose this will save some small amount of code size and complexity, 
but not enough to break even a small amount of content.  I'd be curious 
exactly how much code size this would actually save.  (For those who 
have already implemented it, it would actually be more work to take it 
out, so I don't think this saves effort.)

This strikes me as just the opposite of what the WebApps WG has as one 
of its core missions: specifying what already exists to interoperably 
support a wider array of existing content.

I'm CCing Andrew Sledd of Ikivo and Lee Martineau of QuickOffice 
(formerly BitFlash), who might have a better idea of how much SVG Tiny 
1.2 content uses these methods, hopefully with some pointers to it.

If there is some significant amount of content (e.g. SVGT1.2 content) 
that uses it, even if that content is currently in a walled garden (as 
much mobile content seems to be even today), this would prevent that 
content from working on the wider Web even if it would otherwise.  As 
these walled gardens break down the walls, which is happening today, 
wouldn't it be better to be able to support that content?

-Doug Schepers
W3C Team Contact, SVG and WebApps WGs

Jonas Sicking wrote (on 7/26/09 4:52 PM):
> On Sun, Jul 26, 2009 at 4:36 AM, Anne van Kesteren<>
> wrote:
>> On Sun, 26 Jul 2009 07:55:10 +0200, Jonas Sicking<>
>> wrote:
>>> On Wed, Jul 22, 2009 at 9:35 AM, Anne van
>>> Kesteren<> 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.
> / Jonas

Received on Sunday, 26 July 2009 23:32:35 UTC