- From: Johannes Wilm <notifications@github.com>
- Date: Thu, 11 Dec 2025 06:16:15 -0800
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 11 December 2025 14:16:19 UTC
johanneswilm left a comment (w3c/editing#496) We have not defined the exact dom changes that will be triggered by user action even if we have understood the intention of the user (and capture it by emans of an `inputType` of a (before)InputEvent. This is to allow for plaform specific behavior. In this case, the `div.editable-field` is within the `contenteditable` element and if I understand the report correctly, all the dom changes happen within the `contenteditable` element. Therefore it seems like this is simply platform specific behavior that is spec compliant. That being said, it does seem a bit strange that a div will be destroyed as the user is editing a composition inline. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/496#issuecomment-3642135288 You are receiving this because you are subscribed to this thread. Message ID: <w3c/editing/issues/496/3642135288@github.com>
Received on Thursday, 11 December 2025 14:16:19 UTC