agreed. For those events that are defined elsewhere we should simply decide
how to reference them.
I believe the new UI Events discusses how they get dispatched. This was
published today actually: http://www.w3.org/TR/2013/WD-uievents-20130725/
Good for us.
Rich Schwerdtfeger
From: Cameron McCormack <cam@mcc.id.au>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS,
Cc: Doug Schepers <schepers@w3.org>, "Smailus, Thomas O"
<Thomas.O.Smailus@boeing.com>, "Tab Atkins Jr."
<jackalmage@gmail.com>, "public-svg-wg@w3.org"
<public-svg-wg@w3.org>
Date: 07/24/2013 06:27 PM
Subject: Re: click vs activate
Richard Schwerdtfeger wrote:
> Alright. If the group agrees we should redo the event section to reflect
> this. Additionally, there is new UI Event spec. about to be a public
> working draft, which I referred to when I added keyboard events that we
> should fold in more completely. This is the replacement for DOM3 events.
>
> If we do deprecate DOMActivate and mutation events we should define
> deprecated - gone or being phases out.
>
> Blink wants to remove the mutation events and I don't believe they are
> supported in IE today.
We should be defining as few events as possible in that chapter. Events
that are defined elsewhere can be referenced, and we should say when
they get dispatched, but there is no need for duplicate definitions.
