-
Notifications
You must be signed in to change notification settings - Fork 51
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, as per DOM (http://dom.spec.whatwg.org/#dom-range-detach). #24
Comments
this package is just a simple wrapper for x-editable - any updates to x-editable are outside of the scope of this repo/package - take a look here https://github.com/vitalets/x-editable/issues -- i didnt see anything related to rangy with a quick search though |
Hm, sorry for that and thank you for the package! So, if the maintainers update the package someday the warning will disappear. Since they already have issues enough, I'm not going to create a issue there. |
no worries - yeah, x-editable would have to be updated, then i'd pull in On Mon, Sep 29, 2014 at 8:30 PM, Ernesto Rocha notifications@github.com
|
I could be wrong but I think that this issue is coming from wysihtml5. It has been fixed in version 0.3.3 but you are using 0.3.0. Look at this: Waxolunist/bootstrap3-wysihtml5-bower#88 |
Hello. Thank you for the package. |
I believe that the version of Rangy used by this project is causing this warning in Chrome as you can see here timdown/rangy#223.
Warning:
Can you update Rangy, please ?
The text was updated successfully, but these errors were encountered: