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

Ok, I think there is not all that much disagreement about this then afterall. @fredck I understand your idea and I think it's a good thing to have a way to enable all modules once we have several different modules that could be enabled. However, it would probably be best to use another keyword for this so that browser makers don't have to choose between keeping the old cE=true and the new cE=all.

I propose that at the Paris F2F meeting, we formally deprecate cE=true and take a formal decision not to spec it, after we decide on a cE=intent spec.

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