Re: [w3c/uievents] TPAC 2026 Status Report (Issue #418)

siusin left a comment (w3c/uievents#418)

### Proposed Plan Following the TPAC WebApps WG Discussion

UI Events Content | Recommendation | Proposed Output Specification / Action Items
-- | -- | --
1.1.1. Mouse and Wheel Events | These definitions have been moved to the Pointer Events specification. See w3c/pointerevents#564. | Maintained by the [Pointer Events WG](https://github.com/w3c/pointerevents/).
3.2. User Interface Events | Merge into HTML Standard. | action: file issues in [whatwg/html](https://github.com/whatwg/html). 
3.3. Focus Events | Move focus events to HTML | action: file issues in [whatwg/html](https://github.com/whatwg/html).
3.4. Input Events | Continue the work to separate Input Events from UI Events. See w3c/input-events#184. | Input Events Level 2, maintained by the Web Editing WG. Editor: @johanneswilm
3.5. Keyboard Events, 3.6. Composition Events and 4. Keyboard Events and Key Values | work on a Keyboard Events, Keyboard Key Values, and Composition Events specification, [keydown](https://www.w3.org/TR/uievents/#keydown) and [keyup](https://www.w3.org/TR/uievents/#keyup) events should be moved here too | potentially maintained by the WebEditing WG. Further testing is needed to improve cross-browser interoperability. @sideshowbarker @siusin 
5.2. Pointer Lock Algorithms | Move the Pointer Lock algorithms into the Pointer Lock specification. | Maintained by the WebApps WG.
Other sections of UI Events | publish an empty specification with a note pointing to these components to avoid confusion. |  @siusin 

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

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