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

siusin left a comment (w3c/uievents#418)

<html><head></head><body><h2><span>Proposed Plan for Splitting the UI Events Specification</span></h2>
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.
3.2. User Interface Events | Retain a simplified UI Events specification with a clearly defined scope. | Maintained by the WebApps WG.
3.3. Focus Events | Move focus management and event-triggering behavior to HTML, while relying on DOM for the generic event dispatch mechanism. | Action: Mike Smith to investigate and coordinate the migration to the HTML Standard and DOM Standard.
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: @Johannes Wilm.
3.5. Keyboard Events and 4. Keyboard Events and Key Values | Develop an independent specification covering keyboard events, key values, and related behavior. Further testing is needed to improve cross-browser interoperability. | Keyboard Events, potentially maintained by the WebApps WG. WG ownership needs to be confirmed.
3.6. Composition Events | Develop an independent Composition Events specification. Further testing is needed to improve cross-browser interoperability. | Composition Events, maintained by the Web Editing WG. Editors: @MikeSmith and @Xiaoqian.
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 | Preserve historical descriptions, legacy content, compatibility information, and material that is no longer actively maintained. | Publish a Legacy UI Events Working Group Note. Editor: @Xiaoqian.

<h3><span>Open Questions</span></h3><ul><li><p><span>Should the simplified UI Events specification remain standalone, and what should its scope be?</span></p></li><li><p><span>Which WG should maintain the new Keyboard Events specification?</span></p></li><li><p><span>What additional cross-browser tests are needed for Keyboard Events and Composition Events?</span></p></li></ul></body></html>## Proposed Plan for Splitting the UI Events Specification

| UI Events Content | Recommendation | Proposed Output Specification / Action Items |
|---|---|---|
| [[1.1.1. Mouse and Wheel Events](https://www.w3.org/TR/uievents/#previous-events)](https://www.w3.org/TR/uievents/#previous-events) | These definitions have been moved to the [[Pointer Events specification](https://www.w3.org/TR/pointerevents4/)](https://www.w3.org/TR/pointerevents4/). See [[w3c/pointerevents#564](https://github.com/w3c/pointerevents/pull/564)](https://github.com/w3c/pointerevents/pull/564). | Maintained by the Pointer Events WG. |
| [[3.2. User Interface Events](https://www.w3.org/TR/uievents/#events-uievents)](https://www.w3.org/TR/uievents/#events-uievents) | Retain a simplified UI Events specification with a clearly defined scope. | Maintained by the WebApps WG. |
| [[3.3. Focus Events](https://www.w3.org/TR/uievents/#events-focusevent)](https://www.w3.org/TR/uievents/#events-focusevent) | Move focus management and event-triggering behavior to HTML, while relying on DOM for the generic event dispatch mechanism. | **Action:** Mike Smith to investigate and coordinate the migration to the HTML Standard and DOM Standard. |
| [[3.4. Input Events](https://www.w3.org/TR/uievents/#events-inputevents)](https://www.w3.org/TR/uievents/#events-inputevents) | Continue the work to separate Input Events from UI Events. See [[w3c/input-events#184](https://github.com/w3c/input-events/pull/184)](https://github.com/w3c/input-events/pull/184). | **Input Events Level 2**, maintained by the Web Editing WG. **Editor:** @Johannes Wilm. |
| [[3.5. Keyboard Events](https://www.w3.org/TR/uievents/#events-keyboardevents)](https://www.w3.org/TR/uievents/#events-keyboardevents) and [[4. Keyboard Events and Key Values](https://www.w3.org/TR/uievents-key/)](https://www.w3.org/TR/uievents-key/) | Develop an independent specification covering keyboard events, key values, and related behavior. Further testing is needed to improve cross-browser interoperability. | **Keyboard Events**, potentially maintained by the WebApps WG. WG ownership needs to be confirmed. |
| [[3.6. Composition Events](https://www.w3.org/TR/uievents/#events-compositionevents)](https://www.w3.org/TR/uievents/#events-compositionevents) | Develop an independent Composition Events specification. Further testing is needed to improve cross-browser interoperability. | **Composition Events**, maintained by the Web Editing WG. **Editors:** @MikeSmith and @Xiaoqian. |
| [[5.2. Pointer Lock Algorithms](https://w3c.github.io/uievents/#external-pointerlock-algorithms)](https://w3c.github.io/uievents/#external-pointerlock-algorithms) | Move the Pointer Lock algorithms into the [[Pointer Lock specification](https://w3c.github.io/pointerlock/)](https://w3c.github.io/pointerlock/). | Maintained by the WebApps WG. |
| [[Other sections of UI Events](https://www.w3.org/TR/uievents/)](https://www.w3.org/TR/uievents/) | Preserve historical descriptions, legacy content, compatibility information, and material that is no longer actively maintained. | Publish a **Legacy UI Events Working Group Note**. **Editor:** @Xiaoqian. |


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

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