Re: [w3c/editing] remove document.designMode (#177)

I am curious about the data. It only explained the first spike was due to switching to a more accurate system, but there is another spike around Mar 22, 2018 for both of them, I doubt that we suddenly get a higher usage for both features, so can we find out the reason behind?

On the other hand, there is a browser behavior mismatch with `document.designMode = 'on'` with shadow DOM cases.

For one [example](https://jsfiddle.net/heywuLc6/3/):
```HTML
<div>
  foo
  <div id=host></div>
</div>
```

```JavaScript
const host = document.getElementById('host');
const shadowRoot = host.attachShadow({mode:'open'});
shadowRoot.innerHTML = '<div>bar</div>'
document.designMode = 'on';
```
Content in shadow DOM (i.e. "bar" in this example) is editable in Firefox (note that shadow DOM support in Firefox is behind a flag `dom.webcomponents.shadowdom.enabled`) and Safari but not editable in Chrome. (Sorry I have no access to Edge, but from [this](https://developer.mozilla.org/en-US/docs/Web/API/Element/attachShadow), Edge has no shadow DOM support yet).

>From [shadow DOM spec](https://w3c.github.io/webcomponents/spec/shadow/#editing)
> The value of the contenteditable attribute must not propagate from shadow host to its shadow trees.

It didn't mention shadow DOM should inherit `document.designMode = 'on'` or not.

If we are not deprecating `document.designMode`, we probably want to standardize this behavior. Not sure if I should open another issue in editing or shadow DOM. Just comment my 2 cents here first.

-- 
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/177#issuecomment-403121780