Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Range.detach is now a no-op #223

Closed
thomasbachem opened this issue Jul 22, 2014 · 1 comment
Closed

Range.detach is now a no-op #223

thomasbachem opened this issue Jul 22, 2014 · 1 comment

Comments

@thomasbachem
Copy link

Chrome 36 shows the following warning in the console when using rangy:

'Range.detach' is now a no-op, as per DOM (http://dom.spec.whatwg.org/#dom-range-detach).

Triggered by:

if (isHostMethod(document, "createRange")) {
    testRange = document.createRange();
    if (areHostMethods(testRange, domRangeMethods) && areHostProperties(testRange, domRangeProperties)) {
        implementsDomRange = true;
    }
    testRange.detach(); // <-- TRIGGER
}
@timdown
Copy link
Owner

timdown commented Jul 22, 2014

I removed that call in commit 601b80c. The latest alpha release on GitHub has the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants