w3c/pointerevents Issues

Last updated Jan 23, 2026, 9:52:35 PM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

36 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time past SLO
#572	Browser compliance (especially re: click)	❌	10.5 years	10.5 years
#599	MouseEvent should have DOMString pseudoElement property like TransitionEvent	❌	10.3 years	10.3 years
#600	Proposal for UIEvent "role" property	❌	10.3 years	10.3 years
#573	Define that click doesn't fire on disabled elements	❌	10.3 years	10.3 years
#574	Firing of click event after mousedown/up has two different definitions	❌	10.1 years	10.1 years
#588	Reduce scroll performance impact of `wheel` listeners	❌	9.3 years	9.3 years
#575	Element for dblclick when dblclick results of two clicks on different elements	❌	9 years	9 years
#577	Can any code be run between mouseup and click handlers?	❌	8.3 years	8.3 years
#578	Activation behavior and click interaction is not specified	❌	8.3 years	8.2 years
#610	Different mousedown behavior between Firefox and Chrome/Safari	❌	7.8 years	7.8 years
#611	Need clarification for when mouseenter/mouseleave should be dispatched for moved elements.	❌	7.6 years	7.6 years
#612	mouseover/mouseout events can repeatedly causing infinite re-layout in some buggy content	❌	7 years	7 years
#593	Change DOM_DELTA_PIXEL to be intended scroll distance instead of exact scroll distance	❌	6.2 years	6.2 years
#594	`wheel` event listeners cannot prevent default scroll only along specific direction	❌	6 years	6 years
#582	Differentiate single click event and double click event	❌	4.9 years	4.9 years
#616	Specify the field values for non-pointer `contextmenu` event	❌	4 years	4 years
#617	`MouseEvent.buttons` explanation of `contextmenu` event should mention about the platform dependency	❌	3.7 years	3.7 years
#583	> Overall, Firefox is the most consistent. Ctrl+click and 2-finger-click should act the same, but Chrome and Safari are not. Safari should send auxclick for non-primary mouse clicks.	❌	3.5 years	3.5 years
#618	New `contextmenu` event definition missing bypass	❌	3.2 years	3.1 years
#597	Define behavior for wheel event group when the initial target is mutated	❌	2.9 years	2.9 years
#598	Define behavior for wheel event group when the scroll is handed off	❌	2.9 years	2.9 years
#629	Inconsistency on cancelability of dbclick	❌	1.8 years	1.8 years
#620	[MouseEvent algorithms] Boundary event dispatch needs to be tied to native down and up events	❌	1.3 years	1.3 years
#520	[PointerEvent algorithms] Remove 1:1 correspondence between Mouse and Pointer boundary events	❌	1.3 years	1.3 years
#521	[PointerEvent algorithms] MouseEvents are created from PointerEvents	❌	1.3 years	1.3 years
#522	[PointerEvent algorithms] Dispatch of click, auxclick and contextmenu events	❌	1.3 years	1.3 years
#584	[event-algo] Remove "6.10. send click event"	❌	1.3 years	1.3 years
#525	Add `handwriting` keyword to `touch-action` CSS property	❌	1.2 years	1.2 years
#621	Mandate a minimum dispatch frequency for continuous UI input events	❌	1.2 years	1.1 years
#622	Button order for MouseEvent.button vs MouseEvent.buttons very easy to miss	❌	1.1 years	1.1 years
#623	Clarify `mousemove` event target if preceding `mouseout`, `mouseleave`, `mouseover` or `mouseenter` event listener removes the `mouseover` target	❌	11.6 months	11.4 months
#550	Clarify what happens if capturing element is changed in a `lostpointercapture` listener	❌	8.5 months	8.3 months
#625	Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events	❌	3.3 months	3 months
#559	PointerEvent WPTs that may need attention	❌	2.9 months	2.6 months
#560	Should the `click` event be retargeted when a <menuitem> is selected via mousedown-drag-mouseup?	❌	2.8 months	2.6 months
#563	Clarify touch/pen click target	❌	1.1 months	3.7 weeks