Tim Down

_From [[email protected]](https://code.google.com/u/107383371366938520460/) on January 01, 2011 05:17:45_ The problem is what the browser does when you select a Range, which Rangy cannot control. Internet Explorer is the biggest problem since...

_From [[email protected]](https://code.google.com/u/102341046603171543275/) on January 01, 2011 07:36:42_ I have tried to add the following to the end of WrappedRange.prototype.refresh function and it fixes it. if (!textRangeIsCollapsed(this.textRange)){ var clone = this.cloneRange();...

_From [[email protected]](https://code.google.com/u/107383371366938520460/) on January 02, 2011 17:07:07_ Using htmlText to test the validity of (and possibly alter) the Range created from a TextRange is an interesting idea. I think I...

_From [[email protected]](https://code.google.com/u/118270485250023051399/) on June 14, 2012 02:37:09_ Hello, is any update regarding this topic? thanks!

_From [[email protected]](https://code.google.com/u/107383371366938520460/) on June 14, 2012 02:56:45_ I haven't prioritised this because: - selection boundaries are inconsistent between browsers anyway and most browsers do not allow selection boundaries to be...

I haven't done anything with this for 1.3. I will tag it for 1.4 but it's low priority.

This is by design. The selection offsets are relative to the value of the textarea in all cases. It does mean that offsets can vary between browsers but I think...

Apologies. I have had other priorities in recent months. I'll get to this as soon as I can.

Apologies. I have had other priorities in recent months. I'll get to this as soon as I can.

I haven't tried Rangy with shadow DOM yet. I intend to do so as soon as I can.