- From: Andreu Botella via GitHub <noreply@w3.org>
- Date: Mon, 12 Jan 2026 22:04:30 +0000
- To: public-pointer-events@w3.org
andreubotella has just created a new issue for https://github.com/w3c/pointerevents:
== Specify the field values for non-pointer `contextmenu` event ==
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 no longer clear what those fields should be set to for context menus not opened via pointer. And different browsers differ: Firefox sets `button` to 0, Chromium to -1, and WebKit (tested with GNOME Web on Linux) to 2. All browsers set `buttons` to 0, and they all seem to set `{client,screen}{X,Y}` to the coordinates where the context menu was opened.
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/616 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 January 2026 22:04:30 UTC