Re: [w3c/editing] Ability to rollback changes after IME, so that editors that manage their own incremental rendering can assume the same DOM as before the IME (Issue #510)

johanneswilm left a comment (w3c/editing#510)

Call 2026-07-09:

> Michael Aufreiter provided an update. After experimenting with the 
EditContext API, he found that it addresses the issue well. Since 
EditContext is expected to gain cross-browser support over time, he 
suggested focusing on that approach rather than continuing to pursue a 
solution based on contenteditable.
Dan Clark agreed, noting that the "manual mode for contenteditable" 
discussed in the issue is effectively what EditContext provides.
Michael also shared observations from following the Wordgard editor's 
development. The project has largely switched to using Input Events, 
with IME composition remaining the primary area that still requires DOM 
mutation observation.
He noted that, from an editor developer's perspective, completing 
support for IME through EditContext is one of the last major pieces 
needed and should be considered a high priority.

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

Message ID: <w3c/editing/issues/510/5279794930@github.com>