Re: Comments on proposed new SC 2.5.3

By definition "click" in JavaScript is a complex event that triggers after
mousedown, then mouseup
clickTriggered by a mouse click: mousedown and then mouseup over an element
source:http://javascript.info/tutorial/mouse-events#complex-events


On Mon, Apr 18, 2016 at 4:06 PM, Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> On 18/04/2016 20:44, David MacDonald wrote:
>
>> Guideline 2.5: Touch and Pointer: Make it easier for users to operate
>> touch and pointer functionality.
>>
>> The new language is:
>>
>>
>>         2.5.3 Up-Event Activation: Single touch and/or pointer
>>         activation is triggered on the up-event, or has at least one of
>>         the following is true (Level A):
>>
>>  1. confirmation is provided which can dismiss activation; or
>>  2. the action is reversible; or
>>  3. a mechanism is available to allow the user to trigger activation on
>>     the up-event; or
>>  4. timing of the event is essential and waiting for the up-event would
>>     invalidate the activity.
>>
>> Note: This is when platform assistive technology that remaps touch
>> gestures is */not /*turned on.
>>
>
> What if I as developer am simply listening to the "click" event in
> JavaScript (and not specifically to any "up" events). Am I passing this?
> Whether the browser/platform fires the click on down or up is outside of my
> direct control. In most cases probably yes (click only fired when finger is
> lifted again from touchscreen / mouse button released), but not something I
> can guarantee/control.
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
>
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>
>