Re: click vs activate

Hi, Rich, Thomas–

This is legacy content from SVG 1.1, which was supposed to be styled differently than new, approved content… but it seems it wasn't.  I argued against this spec approach, in part because of this very type of confusion.

Everything in the Interactivity chapter [1] is pretty much up for discussion, as far as I can tell. So, don't worry if something seems unexpected, just raise the issue, don't fret.

In the case of 'activate', it should be removed, because 'DOMActivate' has been deprecated, and 'click' has been changed to match the use case for 'activate' (and to match implementations).

[1] http://www.w3.org/TR/SVG2/interact.html

Regards–
–Doug

On Jul 23, 2013, at 3:29 PM, "Smailus, Thomas O" <Thomas.O.Smailus@boeing.com> wrote:

> I’d go with ‘activate’ over click, because in, say a touchscreen interface, the tap event would be the equivalent to the click event. 
> ‘activate’ seems more generic.
>  
> Thomas
> -- 
> Thomas Smailus, Ph.D., P.E. 
> Senior Advanced Information Technologist
> Boeing Research & Technology 
> SVG Forum CoP Lead | Intelligent Graphics SVG lead
>  
> EO&T LEAP - 2011 / BR&T HIPO - Cadre 1
> Tel: 425/373-2850      Mobile: 347/SMAILUS (non-Boeing)
> VTC: thomas.o.smailus@vtc.boeing.com
>  
>  
> From: Richard Schwerdtfeger [mailto:schwer@us.ibm.com] 
> Sent: Tuesday, July 23, 2013 3:16 PM
> To: Tab Atkins Jr.
> Cc: public-svg-wg@w3.org
> Subject: Re: click vs activate
>  
> Tab, 
> 
> The Events portion of the SVG2 spec. also states an issue where we are trying to reduce the number of events in general. Do you see any reason for keeping activate whenclick is generally supported by all the browsers? Althoughclick has a device dependent name it performs the same function as activate.
> 
> This would simplify things for developers.
> 
> Rich
> 
> 
> 
> Rich Schwerdtfeger
> 
> <image001.gif>"Tab Atkins Jr." ---07/23/2013 04:28:35 PM---On Tue, Jul 23, 2013 at 1:50 PM, Richard Schwerdtfeger <schwer@us.ibm.com> wrote:
> 
> From: "Tab Atkins Jr." <jackalmage@gmail.com>
> To: Richard Schwerdtfeger/Austin/IBM@IBMUS, 
> Cc: "public-svg-wg@w3.org" <public-svg-wg@w3.org>
> Date: 07/23/2013 04:28 PM
> Subject: Re: DOM Mutation Events
> 
> 
> 
> 
> On Tue, Jul 23, 2013 at 1:50 PM, Richard Schwerdtfeger
> <schwer@us.ibm.com> wrote:
> > I am looking at ineract.html. Is there a reason that the DOM Mutation Events
> > are listed for the SVG DOM? From what I recall, mutation events, are usually
> > generated in a browse layer outside the DOM for performance reasons. I am
> > not sure we need to be including these for SVG Web App. developers.  ... Is
> > anyone using these in the wild?
> 
> Further, note that Mutation Events are being phased out of the web.
> We (Blink) are casually considering eventually just removing them
> entirely, as it would simplify a lot of complicated code.
> 
> Mutation Observers are the correct way to respond to changes.
> 
> ~TJ
>

Received on Tuesday, 23 July 2013 22:41:25 UTC