Re: Switching to DOM3 events

I looked at the TPAC SVG day 1 and 2 minutes and the only mention of
onfocus and onblur was wrt. forwarding to window:
http://www.w3.org/2013/11/15-svg-minutes.html

I also don't see this discussed in webapps:

http://www.w3.org/2013/11/11-webapps-minutes.html
http://www.w3.org/2013/11/12-webapps-minutes.html

Was this discussed separately? ... just trying to get up to speed with the
discusssion.


Rich Schwerdtfeger



From:	"Tab Atkins Jr." <jackalmage@gmail.com>
To:	Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc:	SVG WG <public-svg-wg@w3.org>, SVG public list <www-svg@w3.org>
Date:	11/18/2013 05:02 PM
Subject:	Re: Switching to DOM3 events



On Mon, Nov 18, 2013 at 2:54 PM, Richard Schwerdtfeger
<schwer@us.ibm.com> wrote:
> I started working on the Interaction portion of the spec. where we refer
to
> what events we are going to support. Currently, we refer to DOMFocusIn,
> DOMFocusOut, etc. and these are referred to as Legacy UI Events in DOM3.
>
> DOM3 introduces new event types in addition to many of the existing
events:
>
>
http://www.w3.org/TR/2013/WD-DOM-Level-3-Events-20131105/#event-types-list
>
> Here they break up events into finder detail: focusin, focus, and
focusout
> for example. Since we are moving to DOM3 do we want to support all these
> events from DOM3?

Only if they're actually supported.  Note the discussion during the
F2F about focusin/focusout, and how we want to see if we can drop them
in favor of just focus/blur.  (The difference is that focusin/focusout
fire *before* the elements focuses or blurs, while focus/blur fire
*after*.)

> Also, is it safe to say we should expect to see a mouse click event vs.
> having to use DOMActivate?

Yes, DOMActivate is long dead.  'click' is actually an abstract
activation gesture event.

~TJ