Re: [w3c/editing] Preserving the integrity of the contentEditable's hidden state (#223)

I have read the EditContext proposal and it does look like an interesting effort to standardize the contents of the hidden state we have right now. It makes it easy to modify the EditContext when you have the intent to do so.

However, the complexity of understanding the current context and whether or not a modification to the DOM should or shouldn't change the EditContext will remain a very difficult problem. In the event of new advanced capabilities appearing in the future, relying on this API also means participating in a cat and mouse chase where user code must always catch up with the new latest advanced smart insertion mechanic that is being invented.

An alternate direction is to identify a set of mutations that can be performed on the DOM and where the user agent must do its best to preserve the EditContext as it is, without pushing the burden of knowing what is part of that context on the user code.

Should any further discussion be taken to the other repository or is this still the appropriate place?

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