- From: Doug Schepers <schepers@w3.org>
- Date: Tue, 15 Sep 2009 02:21:48 -0400
- To: www-dom@w3.org
Hi, Folks- Olli Pettay wrote (on 9/14/09 6:13 AM): > > the current draft says that DOMFocusIn/DOMFocusOut are deprecated in > favor of "equivalent event type" focusin/focusout. > And indeed the draft specifies those events similarly, but IE > (in which focusin/focusout are implemented) doesn't handle > the events what way. > focusin is dispatched just before the target gets the focus and > focusout is dispatched just before some other target gets focus. > And if those events are added to the spec, that is how they should work. > > See also http://lists.w3.org/Archives/Public/www-dom/2009JulSep/0072.html > > DOMFocusIn/DOMFocusOut work more like focus/blur. > The only difference is that they bubble. Thanks for the reminder. I have reread the threads about this, and rewritten the section on UI events, particularly with regard to the various focus events. I've added a event order list for focus events, and added details about the 'target' and 'currentTarget' properties for each event, based on my research and tests. I rewrote the descriptions of focusin and focusout to better match the IE behavior as described by Olli and Jacob (and to a lesser extent the MSDN documentation and other sources). I did adapt focusin and focusout to the existing DOM event interfaces a little: rather than add the orginal (and useful) IE 'toElement' and 'fromElement' properties, I mapped them to to the 'target' and 'currentTarget' properties, respectively. As mentioned before, DOMFocusIn and DOMFocusOut are deprecated, because I think the other focus events meet most or all of the use cases outlined (let me know if I'm mistaken). I would appreciate review and comments on this revised section. [1] http://lists.w3.org/Archives/Public/www-dom/2009JulSep/0060.html Regards- -Doug Schepers W3C Team Contact, SVG and WebApps WGs
Received on Tuesday, 15 September 2009 06:22:06 UTC