W3C home > Mailing lists > Public > public-forms@w3.org > July 2009

Re: Deprecating DOMFocusIn/DOMFocusOut

From: Doug Schepers <schepers@w3.org>
Date: Thu, 23 Jul 2009 06:30:38 -0400
Message-ID: <4A683BCE.6060502@w3.org>
To: Anne van Kesteren <annevk@opera.com>
CC: Jacob Rossi <t-jacobr@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Travis Leithead <travil@microsoft.com>, "www-dom@w3.org" <www-dom@w3.org>, public-forms@w3.org
Hi, Anne-

Anne van Kesteren wrote (on 7/23/09 6:12 AM):
>
>> That existing implementations that support DOMFocusIn and
>> DOMFocusOut should continue to do so, to support existing content
>> that uses them,
>
> What existing content? It is far more likely existing content uses
> focus and blur. At least as far as Web browsers are concerned and I
> think it would make sense to evaluate a solution for Web browsers
> here in isolation since not bloating the focus API would be great.

SVG content uses DOMFocusIn, DOMFocusOut, and DOMActivate, particularly 
on mobiles.

I agree that not bloating APIs is a good goal, but unfortunately, we 
have legacy implementations and content to deal with... remember that 
bit about "backwards compatibility", and "paving the cowpaths" (with 
regards to focusin and focusout), and "documenting existing behavior"? 
Do you take those principles seriously, or not?


>> but that all implementation should use the replacement events
>> instead. Unless they have a market need, implementations that don't
>> already support deprecated events should not support them in future
>> versions.
>
> Then I do not see much value in deprecation.

Your employer expressed a different opinion on yesterday's telcon, as 
have many other people.

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Thursday, 23 July 2009 10:30:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:52 UTC