- From: Aryeh Gregor <ayg@aryeh.name>
- Date: Sat, 9 Jan 2016 20:17:09 +0200
- To: Johannes Wilm <johannes@fiduswriter.org>
- Cc: "public-editing-tf@w3.org" <public-editing-tf@w3.org>, "Hallvord R. M. Steen" <hsteen@mozilla.com>, Ryosuke Niwa <rniwa@apple.com>, Frederico Knabben <f.knabben@cksource.com>
On Sat, Jan 9, 2016 at 2:35 AM, Johannes Wilm <johannes@fiduswriter.org> wrote: > PD: I am personally fine with removing contentEditable=True entirely, if browser makers have come to the conclusion that the existing text does not make sense. But last time the question of fixing contentEditable=True vs. inventing something new came up here, others seemed to have stronger opinions about this. > > Just adding a few people to CC who could possibly have an opinion about this. As I think I said elsewhere, unless some implementers' opinions have changed, it makes sense not to bother working on a spec for contenteditable=true (although browsers will have their keep their existing implentations indefinitely for web compat). I think it does make sense to make sure the existing spec is kept somewhere in case someone wants it someday, marked as an unmaintained historical document.
Received on Saturday, 9 January 2016 18:18:00 UTC