根据DOM，'Range.detach'现在是无操作的 [英] 'Range.detach' is now a no-op, as per DOM

问题描述

警告：

$ b在我的控制台中发现了此警告和错误消息$ b

 'Range.detach'现在是一个无操作，按照DOM（http://dom.spec.whatwg.org/#dom-range-detach）。 
  

错误：

 不支持不连续选择。 
  

可以看出： http://rangy.googlecode.com/svn/trunk/demos/cssclassapplier.html

其他javascript / jquery插件（wysihtml5，rangy）也受到了影响，有什么解决办法吗？解决方案

我仍然试图决定怎么做对这个。请参阅这个问题（迁移到GitHub并不完整，对不起）。我认为这对Chrome来说是无益的行为，并且将其删除 a>。

Rangy中的违规代码是一项功能测试，用于确定浏览器是否支持多个范围内的选择（当前主流浏览器，仅限Firefox） 。因为这似乎没有消失，我想我将不得不把它吸了起来，并添加浏览器嗅探，这让我很难过。

更新

我向Rangy添加了一个可怕的浏览器嗅探，并且错误不再出现。

I have been noticing this warning and error message in my console after updating Chrome to 36.0.1985.125.

Warning:

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

Error:

Discontiguous selection is not supported.

Can be seen: http://rangy.googlecode.com/svn/trunk/demos/cssclassapplier.html

Other javascript/jquery plugins (wysihtml5, rangy) have also been affected, any solutions?

解决方案

I'm still trying to decide what to do about this. See this Rangy issue (migration to GitHub not quite complete, sorry). I think it's unhelpful behaviour on the part of Chrome and would like it removed.

The offending code in Rangy is in a feature test that determines whether the browser supports multiple ranges within a selection (of the current mainstream browsers, only Firefox does). Since this doesn't seem to be going away I think I'm going to have to suck it up and add a browser sniff, which makes me sad.

Update

I added a horrible browser sniff to Rangy and the error no longer appears.

这篇关于根据DOM，'Range.detach'现在是无操作的的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！