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

>>    DOM tree such as documents which have two or more body elements

> What is the usecase of having more than one body element?

I don't think that it's not useful for any usual web apps. Such case may be used by attackers since not so tested by each vendor and usually causes crash bugs.

> So maybe we should email all non-open source projects to hear with them?

I don't think so. If we keep designMode as part of web standards, new editing API should treat both designMode and contenteditable equally.  Otherwise, each browser may need to check whether currently handling an input with designMode editor or contenteditable editor.

>> So, creating DOM API might be more reasonable than space separated list attribute.

> If this is only for designMode,

I don't think so. Anyway, contenteditable requires JS to post the data. So, I have no idea that it's better to implement this with complicated new attribute of element.

> There seems to be cases where either now or in the past, one enabled designMode to get around some bug in Gecko. Have you seen this [1] before?

I hope that it was a hack for our old bugs. Our HTMLEditor's event handler also handled wrong events whose target are not for the designMode editor.

-- 
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-401671116