W3C home > Mailing lists > Public > public-webapi@w3.org > March 2006

focus/blur events

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 28 Mar 2006 23:27:07 +0000 (UTC)
To: public-webapi@w3.org
Message-ID: <Pine.LNX.4.62.0603282239140.21459@dhalsim.dreamhost.com>

I spoke to Google engineers about our needs regarding focus events in our 
Web content.

Google currently doesn't use any of the focus events other than "focus" 
and "blur", because those are the only events reliably implemented across 
multiple implementations. However, we would like to. Specifically, "focus" 
and "blur" are difficult to use in anything but the simplest scenarios, 
because they don't bubble and IE doesn't implement the capture phase. This 
has resulted in significant infrastructure being built in our products to 
reimplement the capture phase for IE for these events.

IE does implement two other events, "focusin" and "focusout", which do 
bubble. We would use these, or "DOMFocusIn" and "DOMFocusOut", if they 
were interoperably implemented across multiple implementations. We would 
also be happy with "focus" and "blur" if IE implemented capture.

IE also implements onbeforeactivate, onactivate, onbeforedeactivate, 
ondeactivate, and activeElement. We do use some of these. The events 
bubble and as such are more useful in IE.

Having said all this, it is unclear to me exactly what it means for the 
DOM Events spec to have these events, and so I'm unsure as to whether it 
makes any sense to discuss "adding" or "removing" events from this spec.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 28 March 2006 23:27:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:20 UTC