Tim Down

I've changed the feature test to work on an element inserted at the start of the body rather than the end. Hopefully this will fix the issue.

I think that's a good idea and I will implement it soon. However, I'm intending to release 1.3 before doing that. I could keep tinkering for ever otherwise.

Works fine for me. That path looks wrong though: there's no `lib` directory in the Bower package.

It's hard. A naive implementation would be relatively easy but proper sentence identification is really difficult just in English, without even considering other languages. I did a little googling on...

It can't be denied that the TextRange module scales badly. There is similar, faster but less sophisticated functionality built into Rangy's core: [`getBookmark()`](https://github.com/timdown/rangy/wiki/Rangy-Selection#getbookmarknode-containernode) and [`moveToBookmark()`](https://github.com/timdown/rangy/wiki/Rangy-Selection#movetobookmarkobject-bookmark).

Which version of Rangy? I added a workaround and recent 1.3 releases on GitHub should not display this message. There is no actual error; Chrome is just printing a warning...

@slorber Can you give me some example code to reproduce the issue?

Well, there you go. This is why I never normally use user agent sniffs and another reason why this warning message in Chrome is a bad idea. Now I'm reduced...

You can initialize Rangy manually with `rangy.init()`. Rangy needs the DOM to be usable when it initializes so it can't assume it can initialize immediately.

I like this conceptually, but I'm not sure whether it is the correct thing to do. Current versions of all the major browsers allow you to add child nodes to...