TPAC 2026

TPAC 2026

This is the Web Editing Working Group agenda for TPAC 2026.

Note: This is a work in progress (WIP) and you are welcome to make changes.

All times are in UTC (Dublin local time after daylight saving time ends on 25 October).

These meetings will be conducted in accordance with the W3C Code of Ethics and Professional Conduct.

Thursday 29 October, 09:00–16:45 UTC

• Room: Second Floor - Room 12
• Remote joining instructions: Join the meeting
• IRC: #editing
• Chair: Dan Clark

Agenda

• 09:00–09:15: Welcome, Introductions, and Housekeeping

  • Introductions and meeting goals
  • Review of the agenda and priorities

• 09:15–09:45: Working Group Status and Standards Roadmap

  • Review of the current status of the WG's deliverables
  • Implementation progress and remaining blockers across browsers
  • Priorities for the current charter period, potential new work items

• 09:45–10:45: EditContextAPI

  • From Gaurang Tandon: #152 make EditContexts hosts discoverable from extensions
  • From Dan: #156 Allow lazy / pull-on-demand text and selection updates for EditContext
  • #54 Should we add TextFormat.textColor back?
  • #151 Could canvas-based EditContext be removed?
  • #133 Should beforeinput be fired for composition? If so what should the target ranges be?

• 10:45–11:15: ☕ Break

• 11:15–11:45: Clipboard APIs

  • Review blocking issues
  • Identify the remaining browser bugs
  • From Gaurang Tandon: https://issues.chromium.org/issues/40913972 Chrome and Safari behavior is inconsistent with Firefox's and also inconsistent with the underlying spec itself. This leads to bugs like this one: https://github.com/strictdoc-project/strictdoc/issues/3254 This issue is related but stale: https://github.com/w3c/clipboard-apis/issues/50

• 11:45–12:15: Undo Manager

  • Review the use cases and current state of the proposal
  • Discuss implementation interest and the potential for progress from vendors
  • Identify the minimum next steps needed to move the proposal forward
  • Decide whether to pursue an implementation commitment, further incubation, or another path

• 12:15–12:30: Input Events Level 2

  • Review outstanding specification and implementation issues
  • Discuss browser extension use cases, including grammar checkers and other editing assistants
  • Identify gaps in event behavior and interoperability
  • Agree on follow-up work and owners

• 12:30–13:45: 🍴 Lunch

• 13:45–14:15: Caret Movement and Selection API

  • Review progress on the Caret Movement / Caret Navigation proposal
  • Discuss bidirectional text, mixed-direction content, and language-specific editing behavior
  • Review selection-related issues and implementation constraints
  • Identify concrete next steps for the Community Group and Working Group
  • #361 anchorNode & focusNode can never be in shadow tree?

• 14:15–15:00: execCommand — Is There a Path Forward?

  • Review the original motivation for execCommand and the problems it was intended to solve
  • Discuss fundamental limitations of browser-managed editing behavior, including interoperability and language-specific issues
  • Evaluate whether there are concrete use cases that justify further standardization
  • Determine whether to define a limited scope for further work, document the limitations, or defer the topic pending stronger implementation interest
  • From Gaurang Tandon: https://github.com/w3c/editing/issues/200 Chrome's behavior is inconsistent with Firefox and is inconsistent with what was discussed in the GitHub issue itself. From a browser interop perspective, Chrome should update this.

• 15:00–15:30: ☕ Break

• 15:30–16:15: UI Events and Composition Events

  • Develop a Plan to Split the UI Events Spec
  • Discuss the scope and structure of a separate Composition Events specification
  • Identify coordination needs and follow-up actions
  • From Gaurang Tandon: https://github.com/w3c/uievents/issues/220
  • From Gaurang Tandon: https://issues.chromium.org/issues/40666368 This is a bug in Chrome against the spec and inconsistent with Firefox.

• 16:15–16:35: Other Editing Issues and Open Discussion

  • Topic proposal: Current state of Shadow DOM in CKEditor 5
  • Additional issues proposed by participants
  • Follow-up topics related to clipboard, selection, and editing behavior
  • Identify any topics requiring separate discussion sessions

• 16:35–16:45: Wrap-up and Next Steps

  • Summarize key outcomes and decisions
  • Confirm action items, owners, and expected follow-up
  • Identify topics for future WG meetings