[w3c/uievents] Specify the field values for non-pointer `contextmenu` event (Issue #323)

Back when the `contextmenu` event was defined in the HTML spec (see whatwg/html#7505 for context), it used the ["fire a synthetic pointer event"](https://html.spec.whatwg.org/multipage/webappapis.html#fire-a-synthetic-pointer-event) algorithm for context menus opened via keyboard or other non-pointer input, as it does with non-pointer `click` events. This algorithm would set the event's `button{,s}` and `{client,screen}{X,Y}` fields to 0.

With the move of the `contextmenu` event to this spec, it is not clear what those fields should be set to for context menus not opened via pointer. And different browsers differ: Firefox sets `button` and `buttons` to 0; Chromium sets `button` to -1 and `buttons` to 0, and WebKit (tested with GNOME Web on Linux) sets `button` to 2 and `buttons` to 0. All browsers seem to set `{client,screen}{X,Y}` to the coordinates where the context menu was opened.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/323
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/uievents/issues/323@github.com>