Re: [editing] What to do with contentEditableTrue? (#54)

I would vote for option 1.
I would not want to touch CE="true" with a ten-foot poll. Don't spec it and deprecate it once CE="typing/intent/etc" is stabilized.
There is a good reason why CE="true" wasn't specced before. There are too many edge cases that are extremely difficult to cover. In addition, knowing that we are slowly steering away from CE="true", it would be very hard to convince my developers to potentially change its behavior because they would rather work on new features of CE="typing" instead. Any CE="true" work will eventually become a throw away work. And even if we were to implement changes to CE="true", I am not sure how its ripples affect the web.
Modularity idea also resonates with me as we can actually take action on separate modules and can actually define their behavior in the reasonable amount of time. 



---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/54#issuecomment-124774729