Re: [selection-api] Why does getRangeAt must return a reference to (not a copy of) the range? (#40) from Ryosuke Niwa on 2015-01-06 (public-webapps-github@w3.org from January 2015)

From: Ryosuke Niwa <notifications@github.com>
Date: Tue, 06 Jan 2015 14:19:27 -0800
To: w3c/selection-api <selection-api@noreply.github.com>
Message-ID: <w3c/selection-api/issues/40/68944751@github.com>

I think the point of this spec. is agree on these API differences.  Since this behavior is observable by JavaScript and Web apps could rely on one behavior or other, it would be good to agree on one behavior.

https://bugzilla.mozilla.org/show_bug.cgi?id=671152 suggests that Mozilla is interested in changing their behavior to return a clone.

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

Received on Tuesday, 6 January 2015 22:21:41 UTC