Skip to content

Clarify that click, auxclick and contextmenu get their .button and .buttons behavior from UIEvents, https://github.com/w3c/pointerevents/issues/513 #531

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
patrickhlauke merged 2 commits into from
Jan 29, 2025
Merged

Clarify that click, auxclick and contextmenu get their .button and .buttons behavior from UIEvents, https://github.com/w3c/pointerevents/issues/513 #531

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1a9d0cf
Clarify that click, auxclick and contextmenu get their .button and .b…
smaug---- Dec 4, 2024
7bca924
Update index.html
patrickhlauke Jan 29, 2025
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -387,7 +387,7 @@ <h3>Button states</h3>
<h4><dfn data-lt="chorded buttons">Chorded button interactions</dfn></h4>
<p>Some pointer devices, such as mouse or pen, support multiple buttons. In the [[UIEVENTS]] Mouse Event model, each button press produces a <code>mousedown</code> and <code>mouseup</code> event. To better abstract this hardware difference and simplify cross-device input authoring, Pointer Events do not fire overlapping {{GlobalEventHandlers/pointerdown}} and {{GlobalEventHandlers/pointerup}} events for chorded button presses (depressing an additional button while another button on the pointer device is already depressed).</p>
<p>Instead, chorded button presses can be detected by inspecting changes to the <code>button</code> and <code>buttons</code> properties. The <code>button</code> and <code>buttons</code> properties are inherited from the {{MouseEvent}} interface, but with a change in semantics and values, as outlined in the following sections.</p>
<p>The modifications to the <code>button</code> and <code>buttons</code> properties apply only to pointer events. For any <a>compatibility mouse events</a> the value of <code>button</code> and <code>buttons</code> MUST follow [[UIEVENTS]].</p>
<p>The modifications to the <code>button</code> and <code>buttons</code> properties apply only to pointer events. However for <code>click</code>, <code>auxclick</code> and <code>contextmenu</code> the value of <code>button</code> and <code>buttons</code> MUST follow [[UIEVENTS]], as is the case for <a>compatibility mouse events</a> .</p>
</section>
<section>
<h4>The <code>button</code> property</h4>
Expand Down