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

contentEdtiable=plaintext-only is used a fair bit, so I think the only choice available is to standardize it. We had previously discussed this with other browser vendors. IIRC, there was general support, but there were some open questions that never ended up getting resolved.

1. When you hit enter, does it insert a \n like textarea, or a <br>, <div>, <p> like contentEditable? Should it depend on your white-space value? Browsers are pretty inconsistent here with regular contentEditable.
2. We'll also need to specify what it means to "only allow input of plaintext." For example, pasting/dropping in rich content needs to be plain-textified.
3. We'll need to be clear on what it means to ignore a formatting command. For example, it should include that things like ctrl+b shouldn't fire the beforeInput/input events.

In either case, I think speccing something and having unresolved notes in the spec for the above three issues is better than having nothing.

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