Re: [w3c/selection-api] Let addRange not update existing range (#80)

As a WebKit maintainer, I don't have a strong opinion about this. It's a compatibility risk for WebKit to change the behavior so I mildly dislike the change but we can make the change if there are no compatibility problems. But since I'm not strongly opinionated about this matter, I'm not motivated to make this change in WebKit first (although I'm not strongly opposed to it either, and will make the same change for a better interoperability if Blink successfully adopts the new behavior if we don't also encounter compatibility issues).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/80#issuecomment-279909553

Received on Wednesday, 15 February 2017 03:46:59 UTC