W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2014

Re: ACTION-68: Proposed text for "contextmenu issue"

From: Arthur Barstow <art.barstow@nokia.com>
Date: Wed, 29 Jan 2014 08:48:35 -0500
Message-ID: <52E906B3.1010802@nokia.com>
To: Rick Byers <rbyers@google.com>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>
On 1/28/14 12:09 PM, ext Rick Byers wrote:
> Regarding: https://www.w3.org/2012/pointerevents/track/actions/68
>
> How about:
> "Note that the relative order of these high-level events (click, 
> contextmenu, focus, blur, etc.) with pointer events is undefined and 
> varies between user agents."
>
> Perhaps we want to define some term for "high-level" (or "semantic 
> input events") earlier in the the paragraph as part of Jacob's work to 
> expand it (and encourage the use of these sorts of events when 
> appropriate).
>
> We could go on with a more concrete example like the following, but I 
> think it's probably overkill:
> "For example, on some user agents contextmenu will often follow a 
> pointerup, on others it'll often proceed a pointerup or pointercancel, 
> and in some situations it may be fired without any corresponding 
> pointer event".

The proposed text looks ok to me and I think the example adds value.

I probably wouldn't define "high-level" although as you say, doing so 
might make sense depending on Jacob's impending work in this area.

(Potential nit: s/proceed/precede/ in the example text but not sure.)

-AB
Received on Wednesday, 29 January 2014 13:49:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:26 UTC