Re: Feedback on 07 September 2010 draft re DOMActivate

On Wed, Nov 17, 2010 at 1:34 AM, Dan Burnett <dburnett@voxeo.com> wrote:
> Thanks for your reply, Jonas.  I notice that while your arguments speak
> strongly in favor of having an event named "click" with the semantics of
> "device independent abstract event with the meaning of activation", I do not
> see a single argument against *permitting* the existing synonym called
> "DOMActivate".
>
> Interestingly, you say "The goal here has been one of accessibility" and go
> on to imply that we wish to "reeducate everyone".  If you'll notice, our
> request was not to remove "click" nor to change anyone else's mind about how
> to use it -- rather, our request was not to deprecate the use of
> DOMActivate.  If you are interested in accessibility and broad adoption,
> what have you to fear from supporting both names?

Hi Dan,

DOM Level 3 Events explicitly allows you to fire DOMActivate. Quoting
from the spec:

"Other specifications may define and maintain their own DOMActivate
event type for backwards compatibility".

So if you want to keep using DOMActivate neither me nor the DOM Level
3 Events spec is standing in your way.

However note that there is a large body of web developers out there
who think of "click" as the "abstract activation" event. Also note
that in HTML "click" is the abstract activation event. So if you want
to attract web authors, or if you write specifications which might
interact with HTML, then it *could* be beneficial to consider
transition from "DOMActivate" to "click".

Obviously such a decision is entirely up to you and the others working
on the relevant specification. And of course such a transition should
be done in a responsible manner to allow any existing
content/authors/tools to migrate. And it might very well be that this
is not the right decision for your specification in which case you
should feel free to stay with DOMActivate.

Hope that makes things more clear?

/ Jonas

Received on Wednesday, 17 November 2010 18:09:53 UTC