- From: Rich Schwerdtfeger <richschwer@gmail.com>
- Date: Wed, 26 Jul 2017 15:05:28 -0400
- To: Aaron Leventhal <aleventhal@google.com>
- Cc: ARIA Working Group <public-aria@w3.org>
Aaron this was in since before 1.0 when you also contributed and reviewed. It has not changed. If you have readonly true the default must be false. That said you know the use cases - grid, treegrid, any control that would allow the user to change it's contents like a UI design tool. There have also been apps that have implemented their own contenteditable at IBM. That said, Caret location is a problem unless you use an OSM. Generally speaking, contenteditable sucks if you wanted to something more involved like Google docs. I am fairly certain Google docs had not used contenteditable as it was not full function enough. They had created special apis for communicating the caret position to their screenreader Chrome add-on. Also, for the longest time Google had only one editor on contenteditable areas and designmode="true". Cheers, Rich Sent from my iPhone > On Jul 26, 2017, at 11:32 AM, Aaron Leventhal <aleventhal@google.com> wrote: > > Aaron
Received on Wednesday, 26 July 2017 19:05:53 UTC