Re: [w3c/editing] Should contenteditable=plaintext-only be standardized? (#162)

Hey,
yes so 3 of the states in that draft were made for editors as the one you describe @samuelgozi . The reason we had 3 and not just 1 was that IME and some other features like mobile browsing meant that it was difficult for us to choose just one of those states and so we kept all three for now. The last one, `plaintext-only`, could possibly also be used as part of a general editor, but it was really invented by Safari/Chrome to be used by their browser native tools for web developers like the "edit as HTML" feature. So if I recall correctly we left that one alone for the time being as it's being might be dictated by the needs of the browser-specific development consoles and cannot be adjusted to work well in other contexts.

-- 
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/162#issuecomment-615948053