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

This is a blocking issue of removing webkit-user-modify from Blink.

There seems to be an important use case of contenteditable=plaintext-only in Chrome DevTools:

In the "Elements" panel, we can modify a tag (tag name, style, class and other attributes) by doubleclicking at the tag, which turns certain part of the tag plaintext editable (as shown by the attachment
![screenshot from 2017-03-10 13 50 57](https://cloud.githubusercontent.com/assets/19384155/23814868/23e1840c-059a-11e7-863e-0c8cf51fb51c.png)
). When we finish editing, we can click outside or press Esc to switch the editable part back to uneditable.

DevTools currently implements this functionality by making certain element switch between "-webkit-user-modify: read-only" and "-webkit-user-modify: read-write-plaintext-only". There doesn't seem to be an easy way to convert the implementation to follow the standards, as the standards do not provide any means for plaintext editing other than <input> and <textarea>.

If contenteditable=plaintext-only can be standardized, then the above use case can be well supported.

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

Received on Friday, 10 March 2017 22:03:26 UTC