On Mon, Jul 26, 2010 at 12:06 AM, Darin Adler <darin@apple.com> wrote:
Sounds like some differences are:
1) The blur event in Opera and IE will see the new focused node as the active element, but in WebKit and Firefox will see no active element at all. 2) Same for DOMFocusOut, but IE and Firefox are not affected.
Is there a good reason to do blur the Firefox way instead of the Opera/IE way? Maybe because it’s the legacy WebKit way, and hence likely to be depended on by WebKit-tested or WebKit/Firefox-tested content?
The spec seems to require that: http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event... A user agent must dispatch this event when an event target loses focus. The focus shall be taken from the element before the dispatch of this event type. This event type is similar to focusout, but is dispatched after focus is shifted, and does not bubble. Best, Ryosuke