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)

michael left a comment (w3c/editing#510)

As a developer I'd actually very much enjoy a new "completely manual" mode for contenteditable (e.g. `contenteditable="events-only"`). The purpose of this mode would be to give full control over every input to me as an editor developer. 

It would also free us from any breaking changes to existing behavior. Changes in the semantics of the events could only happen in that 'events-only' mode, so no old apps would break.

Use Cases:
- you either want A) contenteditable to `just do its thing` and not interfere with it (that's what browsers already implement well. It works as long as you don't start intercepting events (e.g. composition events)
  - **DOM is the source of truth**
- or you want B) to have full control, have an internal editor model that you update as input events arrive, and then trigger rerenders of the DOM that follow your model
  - **custom editor model is the source of truth** (the DOM is a representation of that state)

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

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