W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Re: [Selection] Should selection.getRangeAt return a clone or a reference?

From: Ryosuke Niwa <rniwa@apple.com>
Date: Tue, 13 Jan 2015 14:29:49 -0800
Cc: "chaals@yandex-team.ru" <chaals@yandex-team.ru>, Boris Zbarsky <bzbarsky@mit.edu>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-id: <3FE5309D-BCBB-435E-8ED7-C45D39FA6C94@apple.com>
To: Arthur Barstow <art.barstow@gmail.com>

> On Jan 13, 2015, at 10:06 AM, Ryosuke Niwa <rniwa@apple.com> wrote:
>> On Jan 13, 2015, at 4:21 AM, Arthur Barstow <art.barstow@gmail.com> wrote:
>>> On 1/13/15 6:54 AM, chaals@yandex-team.ru wrote:
>>> 13.01.2015, 05:31, "Boris Zbarsky" <bzbarsky@mit.edu>:
>>>>> On 1/12/15 1:56 PM, Olivier Forget wrote:
>>>>> Unfortunately
>>>>> multiple range selections are not a "nice to have". All "real" editors
>>>>> (MS Word, Google Docs, etc..) support selecting multiple ranges
>>>> Precisely.  This is why Gecko ended up supporting it: it was needed for
>>>> the editor that was part of the Mozilla suite back in the day....
>>>> Of course I've made this point before; it just got ignored.  :(
>>> :(
>>> And yeah, painful as it may be to implement in the browser, I suspect in the long run it is the right answer.
>> If the `plan of record` is to not explicitly address selecting multiple ranges in the first version of the spec, perhaps a new issue should be created (with an `enhancement` tag).
>> (I didn't notice such an Issue in <https://github.com/w3c/selection-api/issues?q=is%3Aopen+is%3Aissue> and will gladly create one if folks confirm that is the consensus and expectation.)
> Indeed, someone who feel strongly about this feature (multi-range selection) should feel a new issue.

Filed https://github.com/w3c/selection-api/issues/41 <https://github.com/w3c/selection-api/issues/41> to track this.

- R. Niwa
Received on Tuesday, 13 January 2015 22:30:18 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC