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

Here is a clarifying note to emphasize why I believe this issue is important. I used a single example where a contentEditable element's hidden state is being interfered with when programmatic changes but there is a wide array of such cases. Here is a non-exhaustive list of such cases:

1. Normal text insertion leads to autocomplete/autocorrect proposals being displayed to the user
1. Swipe insertion leads to alternate proposals being displayed to the user
1. Swipe insertion may provide autocorrect suggestion based on the two previous words (swipe insert "out home" and iOS suggests "our home" as a replacement)
1. Normal text insertion knows to insert a space before a new character after a swipe insert has occured
1. etc.

-- 
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-560938974