W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2009

Re: CfC: FocusEvent Interface

From: Doug Schepers <schepers@w3.org>
Date: Wed, 23 Sep 2009 00:27:23 -0400
Message-ID: <4AB9A3AB.7000501@w3.org>
To: "www-dom@w3.org" <www-dom@w3.org>
Hi, Maciej-

Maciej Stachowiak wrote (on 9/22/09 9:34 PM):
>
> The FocusEvent interface itself seems fine, and a good solution.

Thanks for the suggestion.  You were on the money.


> I do think it would be worth doing some cursory research to determine
> whether it is a problem to support "focusin" and "focusout" events
> without 100% API compatibility with IE. Do sites only use these in
> IE-specific code paths currently, or is it possible that they register
> and use IE-specific APIs?

As Garrett alluded (IIUC), they might even use the presence of these 
attributes to detect the feature for slipping into that code path.  Not 
a great practice, but there you have it (and admittedly better than 
browser sniffing).


> These questions are relevant, because we may want to support IE's
> toElement and fromElement attributes in the standard, depending on the
> results.

Sadly, I agree.

Garrett's analysis seems pertinent here.  It would be good to research 
it a bit deeper to make sure it actually does cause the problems he 
described.

Fortunately, moving it to the new FocusEvent would let us add the 
toElement and fromElement attributes without disrupting other 
interfaces, so that's another good thing about your model.  I'll 
tentatively add them, unless others have objections to that plan.

I would especially like to hear from Microsoft, since they have the most 
experience dealing with content that uses them, I'd expect.

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Wednesday, 23 September 2009 04:27:34 GMT

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