Chrome and Firefox isusses with range

[voog]

Chrome and Firefox isusses with range

[kasoban]

Are you sure this is related to the upgrade to 0.4.12? I encountered a very similar problem before which was related to the rangy core module. I can not find the issue/pull request where I fetched this solution from, but look for the line

sel._ranges.length = sel.rangeCount = sel.nativeSelection.rangeCount;

and change it to

sel._ranges.length = sel.rangeCount = (sel.nativeSelection ? sel.nativeSelection.rangeCount : 0);

This fixed my firefox issues.

Edit: Now I remember where I've seen this before. You already had that same error before and reported it here: #32

It just looks different at first because you used the minified version at the time.

[Themonkey180]

Thank you for that fixes. It fixed the Firefox issues which were the biggest issue, but I still have the one in chrome to fix.

[bhaak]

The nativeSelection issue seems to be related to these Firefox bugs: https://bugzil.la/495230, https://bugzil.la/827585

Although Firefox is violating the spec, judging from the last comment in the second bug report, it's not likely to get fixed soon in Firefox, so the workaround @kasoban used seems to be the way to go for the time being.

[Nyholm]

Any updates on this? I'm using version 0.5.0-beta8 and I do also get the following error in Chrome.
The given range and the current selection belong to two different document fragments.

[naoisegolden]

+1

[kieranklaassen]

+1