On Tue, Jul 27, 2010 at 10:37 AM, Darin Adler da...@apple.com wrote:
This sequence doesn’t sound too terrible to me. But I don’t fully
understand the proposal. At the time the focusin event fires we won’t yet
know what item is getting focus?
I think we do know this and it wouldn't be too
I think the order as specced at
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-focusevent-event-order
is fine. It seems to solve the ordering from a backwards compatibility
case.
The spec leaves out when document.activeElement is changed though.
erik
On Mon, Jul
On Jul 26, 2010, at 6:32 PM, Ojan Vafai wrote:
On Mon, Jul 26, 2010 at 12:06 AM, Darin Adler da...@apple.com wrote:
You mention activeElementId, but there must be other side effects that matter.
The only other side effects I can think of are the focus outline (which could
probably be
On Jul 21, 2010, at 5:24 PM, Ojan Vafai wrote:
Opera 10.6: blur, domfocusout, focus, domfocusin
Moves activeElement immediately before firing any events.
WebKit nightly: blur, (dom)focusout, focus, (dom)focusin
Clears activeElement before blur/focusout, sets active element before
On Wed, Jul 21, 2010 at 5:24 PM, Ojan Vafai o...@chromium.org wrote:
Opera 10.6: blur, domfocusout, focus, domfocusin
Moves activeElement immediately before firing any events.
WebKit nightly: blur, (dom)focusout, focus, (dom)focusin
Clears activeElement before blur/focusout, sets active
On Mon, Jul 26, 2010 at 12:06 AM, Darin Adler da...@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
There are a few concerns on the table:
1. We don't match the DOM3 spec. I'm not too worried about this. Neither
does anyone else. We could probably get the spec to change if noone is going
to implement it as is.
2. We don't match other browsers. It's not clear to me what changes are
worth making
WebKit doesn't match the DOM 3 spec WRT focusin/focusout events, see
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-focusevent-doc-focus
. Specifically, focusin/focusout are supposed to fire before the element
actually receives/loses focus. Browsers are wildly
8 matches
Mail list logo