Re: [w3c/editing] contenteditable-disabled (#176)

> I don't think so. If we keep designMode as part of web standards, new editing API should treat both designMode and contenteditable equally. 

Well, in order to see whether there is any point in continuing with designMode, we should try to find out if anyone has a realworld usecase for it. I notice that CKEditor and TinyMCE used it in the past, but switched to contenteditable more than half a decade ago. One thing is keeping designMode around so that certain old websites don't break, but it's something else to add more features to it.

So I think we should find out: Is anyone using it for production, and if so: what is stopping them from moving to contenteditable? Having a document where the body element is exchanged is in itself not a usecase as long we don't know why anyone would do that, but maybe we can find a usecase where it is important to switch out the body element like that and not being able to add other attributes to the body element.

> I hope that it was a hack for our old bugs.

Ok, I'll try to email them and ask what is going on there.

-- 
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/176#issuecomment-402215383