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

Re: Deprecating DOMFocusIn/DOMFocusOut

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 23 Jul 2009 10:40:45 -0400
Message-ID: <4A68766D.9050606@mit.edu>
To: Jacob Rossi <t-jacobr@microsoft.com>
CC: Doug Schepers <schepers@w3.org>, Anne van Kesteren <annevk@opera.com>, Maciej Stachowiak <mjs@apple.com>, Travis Leithead <travil@microsoft.com>, "www-dom@w3.org" <www-dom@w3.org>, "public-forms@w3.org" <public-forms@w3.org>
Jacob Rossi wrote:
> Yes, so in response to that action, here's how IE handles focus events:
> 
> focus, blur, focusin, and focusout can be registered on any element which is "focusable."
> 
> During a focus change from elementA to elementB, the following events are fired in this order:
> 
> 1. focusout:   srcElement is elementA, toElement is elementB, bubbles, not cancelable
> 2. focusin:  srcElement is elementB, fromElement is elementA, bubbles, not cancelable
> 3. Focus changes from elementA to elementB
> 4. blur: srcElement is elementA, does not bubble, not cancelable
> 5. focus: srcElement is elementB, does not bubble, not cancelable

That's a great start (assuming we want to spec focusout/focusin).  We 
also need to spec what happens if a handler during any of steps 1, 2, 4, 
5, calls focus() or blur() on some element (possible cases being 
elementA, elementB, elementC).  That's been by far the biggest source of 
compatibility problems we've run into with Gecko.

-Boris
Received on Thursday, 23 July 2009 14:41:49 UTC

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