[selection-api] Why does getRangeAt must return a reference to (not a copy of) the range? (#40)

The spec currently say:

> it must return a reference to (not a copy of) the context object's range.

and in its following note, it says it's currently not interoperable. Are there any reasons or good use cases to make this a "must" when implementations are not interoperable?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/40

Received on Tuesday, 6 January 2015 05:30:34 UTC