Initial attempt at fixing a bug on Android Chrome that shows up when an editable is blurred. It looks like in some cases the saved native range is altered and so gets out of sync with the rangy range. In the cases where I've seen this it's the native range that is wrong. The browser seems to be doing odd things like moving the selection on/back a word when the editable is blurred. It definitely looks wrong but it's hard to work out exactly when this happens and why. This fix assumes it only happens on Android Chrome as that's the only place i've seen it happen so far. Feature checking would be better (obviously) but so far I've been unable to reliably produce a test case that always shows the problem.
Add a new example that helped me identify the issue.
Code will be tidied up if more testing shows that this is a useful fix.
Tidy.
Throttle the selection change event handler which greatly improves performance on Android Chrome.