Chrome: 'Range.detach' is now a no-op, as per DOM about wysihtml

[dhoulb]

I'm getting the same thing. Happens on DOM load (before I've instantiated a WYSIWYG area). I'm guessing it's part of some browser compatibility testing that WYSIHTML5 or Rangy does early on.

I'm also getting a The given range and the current selection belong to two different document fragments. error, which I assume is related.

[timdown]

Rangy does do feature tests during initialization which cause recent Chrome to warn both "'Range.detach' is now a no-op, as per DOM" and "Discontiguous selection is not supported.". The latest version of Rangy on GitHub has workarounds for both.

[adantart]

just a question, do we have to upgrade Rangy by ourselves or are you going to upgrade the lib here ?

[timdown]

Is that directed at me, @adantart? If so then I'm happy to create a pull request with the latest version of Rangy but I'd have thought it would be just as simple to download the latest release from https://github.com/timdown/rangy/releases and do it yourselves.

[adantart]

Yes, I know it's that simple, but just wanted to know if I have to, or better to wait the main project (yours) to do it, and then I upgrade yours ;-)
It's not about "who" is doing this, but having a clean repository dependencies. I prefer to upgrade your package when it's upgraded, if not, I will have conflicts when I upgrade yours after changing a library inside it.

[kasoban]

@adantart I think there is some misunderstanding here, @timdown is not the maintainer of Edicy/wysihtml5 but of Rangy