public-pointer-events@w3.org from January to March 2026 by date

Sunday, 25 January 2026

• Re: [pointerevents] Should a captured pointer send boundary events by default? (#566) Scott González via GitHub

Friday, 23 January 2026

• Re: [pointerevents] Clarify touch/pen click target (#563) sb3nder via GitHub

Wednesday, 21 January 2026

• [pointerevents] Pull Request: Update link to implementation report for pointerevents3 Philippe Le Hegaret via GitHub

Tuesday, 20 January 2026

• PE3 implementation report Philippe Le Hégaret
• Re: [pointerevents] Should WheelEvent definitions move to PointerEvent? (#557) Philippe Le Hegaret via GitHub
• Closed: [pointerevents] Should WheelEvent definitions move to PointerEvent? (#557) Philippe Le Hegaret via GitHub

Thursday, 15 January 2026

• Closed: [pointerevents] Behavior of PointerEvent.fromElement/toElement (#167) Mustaq Ahmed via GitHub
• Re: [pointerevents] Behavior of PointerEvent.fromElement/toElement (#167) Mustaq Ahmed via GitHub
• Re: [pointerevents] Pointerevents+UI events (#564) Philippe Le Hegaret via GitHub
• Re: [pointerevents] Pointerevents+UI events (#564) Philippe Le Hegaret via GitHub
• Re: [pointerevents] Pointerevents+UI events (#564) Philippe Le Hegaret via GitHub

Wednesday, 14 January 2026

• Re: [pointerevents] Behavior of MouseEvent.fromElement/toElement (#167) Chris Rebert via GitHub
• Re: [pointerevents] Behavior of MouseEvent.fromElement/toElement (#167) Mustaq Ahmed via GitHub
• Re: [pointerevents] Behavior of MouseEvent.fromElement/toElement (#167) Chris Rebert via GitHub
• Re: [pointerevents] MouseEvent.fromElement/toElement (#605) Mustaq Ahmed via GitHub
• Minutes from PEWG meeting 14 January 2026 Patrick H. Lauke
• Re: [pointerevents] Pointerevents+UI events (#564) Robert Flack via GitHub
• Re: [pointerevents] Pointerevents+UI events (#564) Philippe Le Hegaret via GitHub
• Re: [pointerevents] Pointerevents+UI events (#564) Philippe Le Hegaret via GitHub
• Re: [pointerevents] MouseEvent.fromElement/toElement (#605) Mustaq Ahmed via GitHub
• Closed: [pointerevents] MouseEvent.fromElement/toElement (#605) Mustaq Ahmed via GitHub

Tuesday, 13 January 2026

• Event Updated: Pointer Events WG call Patrick Lauke (W3C Calendar)
• Re: [pointerevents] Pointerevents+UI events (#564) Philippe Le Hegaret via GitHub
• Re: [pointerevents] Pointerevents+UI events (#564) Philippe Le Hegaret via GitHub
• Closed: [pointerevents] Define what layerX/layerY do in presence of transforms. (#627) Mustaq Ahmed via GitHub
• Re: [pointerevents] Define what layerX/layerY do in presence of transforms. (#627) Mustaq Ahmed via GitHub
• Re: [pointerevents] Pointerevents+UI events (#564) Philippe Le Hegaret via GitHub
• Re: [pointerevents] Clarify touch/pen click target (#563) sb3nder via GitHub
• Re: [pointerevents] Pointerevents+UI events (#564) Philippe Le Hegaret via GitHub
• Re: [pointerevents] Define what layerX/layerY do in presence of transforms. (#627) Chris Harrelson via GitHub

Monday, 12 January 2026

• [pointerevents] Different click event order behavior between Firefox , ie , edge and Chrome/Safari (#634) PingChuanXi via GitHub
• [pointerevents] Specify WheelEvent.wheelDelta / wheelDeltaX / wheelDeltaY (#633) Emilio Cobos Álvarez via GitHub
• [pointerevents] Mouse back/forward buttons: page navigation or JS events? (#632) smaug---- via GitHub
• [pointerevents] [feature request] Standardize long press touch event (#631) Thaina Yu via GitHub
• [pointerevents] The specification of `relatedTarget` property of `mouseover` reads "indicates the event target a pointing device is entering, if any." but should read "exiting" (#630) Simon Bates via GitHub
• [pointerevents] Inconsistency on cancelability of dbclick (#629) Dominique Hazael-Massieux via GitHub
• [pointerevents] Back and Forward buttons not specified for MouseEvent.buttons (#628) Pierre Ossman (ThinLinc team) via GitHub
• [pointerevents] Define what layerX/layerY do in presence of transforms. (#627) Emilio Cobos Álvarez via GitHub
• [pointerevents] Standardize layerX/layerY on MouseEvent (#626) Dave Tapuska via GitHub
• [pointerevents] Mention about `<area>` of image map in somewhere, which may be a target of mouse/pointer/touch events (#625) Masayuki Nakano via GitHub
• [pointerevents] Need clarification with `MouseEvent::mouseleave` (#624) Euclid Ye via GitHub
• [pointerevents] Clarify `mousemove` event target if preceding `mouseout`, `mouseleave`, `mouseover` or `mouseenter` event listener removes the `mouseover` target (#623) Masayuki Nakano via GitHub
• [pointerevents] Button order for MouseEvent.button vs MouseEvent.buttons very easy to miss (#622) Pierre Ossman (ThinLinc team) via GitHub
• [pointerevents] Mandate a minimum dispatch frequency for continuous UI input events (#621) Isaac King via GitHub
• [pointerevents] [MouseEvent algorithms] Boundary event dispatch needs to be tied to native down and up events (#620) Mustaq Ahmed via GitHub
• [pointerevents] Clearify whether `mouseover`, `mouseout`, `mouseenter` and `mouseleave` are fired or not fired when the target is removed by `mousedown` or `mouseup` (#619) Masayuki Nakano via GitHub
• [pointerevents] New `contextmenu` event definition missing bypass (#618) Aphek via GitHub
• [pointerevents] `MouseEvent.buttons` explanation of `contextmenu` event should mention about the platform dependency (#617) Masayuki Nakano via GitHub
• [pointerevents] Specify the field values for non-pointer `contextmenu` event (#616) Andreu Botella via GitHub
• [pointerevents] Introduce contextmenuclose or similar event. (#615) Robert Flack via GitHub
• [pointerevents] The order in which the `contextmenu` `auxclick` event is triggered (#614) mantou via GitHub
• [pointerevents] Need clarification how mouseenter/leave should behave while modifying DOM tree during event dispatch (#613) smaug---- via GitHub
• [pointerevents] mouseover/mouseout events can repeatedly causing infinite re-layout in some buggy content (#612) 積丹尼 Dan Jacobson via GitHub
• [pointerevents] Need clarification for when mouseenter/mouseleave should be dispatched for moved elements. (#611) Robert Flack via GitHub
• [pointerevents] Different mousedown behavior between Firefox and Chrome/Safari (#610) Andrea Puddu via GitHub
• [pointerevents] May the state of modifier keys influence MouseEvent.button? (#608) John Firebaugh via GitHub
• [pointerevents] Need algorithm for how mouse events are fired (#609) Gary Kacmarcik via GitHub
• [pointerevents] MouseEvent.screenX/Y coordinate space is not clear (#607) Navid Zolghadr via GitHub
• [pointerevents] Specify the arguments of initMouseEvent() (#606) Philip Jägenstedt via GitHub
• [pointerevents] MouseEvent.fromElement/toElement (#605) Chris Rebert via GitHub
• [pointerevents] Explain that mousedown focuses form controls (#604) Chris Rebert via GitHub
• [pointerevents] Clarify what events are expected from <option> elements in <select> dropdowns (#603) Mike Conley via GitHub
• [pointerevents] Mouse coordinates represented in CSS pixels do not account for retina displays with window.devicePixelRatio > 1 (#602) Gary Kacmarcik via GitHub
• [pointerevents] Specify MouseEvent.which (#601) Gary Kacmarcik via GitHub
• [pointerevents] Proposal for UIEvent "role" property (#600) Gary Kacmarcik via GitHub
• [pointerevents] MouseEvent should have DOMString pseudoElement property like TransitionEvent (#599) Gary Kacmarcik via GitHub
• [pointerevents] Define behavior for wheel event group when the initial target is mutated (#597) Dan Robertson via GitHub
• [pointerevents] Define behavior for wheel event group when the scroll is handed off (#598) Dan Robertson via GitHub
• [pointerevents] Wheel event: determine difference between trackpad and mouse events (#596) Alex Kempton via GitHub
• [pointerevents] Add mousewheel to the "Legacy Event Types" section (#595) Gary Kacmarcik via GitHub
• [pointerevents] `wheel` event listeners cannot prevent default scroll only along specific direction (#594) Masayuki Nakano via GitHub
• [pointerevents] Change DOM_DELTA_PIXEL to be intended scroll distance instead of exact scroll distance (#593) Clay Martin via GitHub
• [pointerevents] Needs alternative WheelEvent.deltaMode, WheelEvent.delta(X|Y|Z) (#592) Masayuki Nakano via GitHub
• [pointerevents] Expose wheel event scrolling state to DOM events (#591) Sahel Sharifymoghaddam via GitHub
• [pointerevents] Add WheelEvent#wheelDelta/wheelDeltaX/wheelDeltaY (#590) Philip Jägenstedt via GitHub
• [pointerevents] WheelEvent.intDelta(X|Y|Z) might be useful for some web apps which cannot scroll its contents smoothly (#589) Masayuki Nakano via GitHub
• [pointerevents] Reduce scroll performance impact of `wheel` listeners (#588) Rick Byers via GitHub
• [pointerevents] Expose 'inertial scrolling state' in wheel events (#587) Loren Brichter via GitHub
• [pointerevents] Expose 'direction-inversion' in wheel events (#586) Loren Brichter via GitHub
• [pointerevents] Expose ticks in wheel events (#585) Gary Kacmarcik via GitHub
• [pointerevents] [event-algo] Remove "6.10. send click event" (#584) smaug---- via GitHub
• [pointerevents] > 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. (#583) mohamedmosseb via GitHub
• [pointerevents] Differentiate single click event and double click event (#582) Jimmy Wärting via GitHub
• [pointerevents] Clarify whether a click event should be dispatched for `control` + click in Mac OS (#581) Edgar Chen via GitHub
• [pointerevents] Click targeting is inconsistent across different UAs and the spec (#580) Navid Zolghadr via GitHub
• [pointerevents] Need algorithm for how mouse click events are fired (#579) Gary Kacmarcik via GitHub
• [pointerevents] Activation behavior and click interaction is not specified (#578) Boris Zbarsky via GitHub
• [pointerevents] Can any code be run between mouseup and click handlers? (#577) Navid Zolghadr via GitHub
• [pointerevents] Click event is not fired when the node is removed and then added back (#576) Navid Zolghadr via GitHub
• [pointerevents] Element for dblclick when dblclick results of two clicks on different elements (#575) Maxence Dalmais via GitHub
• [pointerevents] Firing of click event after mousedown/up has two different definitions (#574) smaug---- via GitHub
• [pointerevents] Define that click doesn't fire on disabled elements (#573) Gary Kacmarcik via GitHub
• [pointerevents] Browser compliance (especially re: click) (#572) Stuart P. Bentley via GitHub
• [pointerevents] Should events queue a task? (#571) Jake Archibald via GitHub
• [pointerevents] Simultaneously move / drag with multiple pointer devices (#570) Stone via GitHub
• [pointerevents] Would be good to better clarify pointer event firing (#569) Boris Zbarsky via GitHub
• [pointerevents] Add attribute tests for nohover pointer events like touch (#568) Navid Zolghadr via GitHub
• [pointerevents] Incorrect movementX/Y in PointerEvents (#567) Navid Zolghadr via GitHub
• [pointerevents] Should a captured pointer send boundary events by default? (#566) Rick Byers via GitHub
• [pointerevents] Add explicit control over pinch-zoom to touch-action (#565) Rick Byers via GitHub
• [pointerevents] Pull Request: Pointerevents+UI events Philippe Le Hegaret via GitHub
• Event Updated: UI Events Task Force Meeting Xiaoqian Wu (W3C Calendar)

Last message date: Sunday, 25 January 2026 16:14:35 UTC