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: Aryeh Gregor <ayg@aryeh.name>
Date: Mon, 12 Jan 2015 13:35:32 +0200
Message-ID: <CAKA+AxmGDkfLXOC+F=D2uoAsOszSJ7wwUU-Rqso+nKQoYfcEnA@mail.gmail.com>
To: Karl Dubost <karl@la-grange.net>
Cc: Olivier Forget <teleclimber@gmail.com>, Ryosuke Niwa <rniwa@apple.com>, Koji Ishii <kojiishi@gmail.com>, Webapps WG <public-webapps@w3.org>
On Mon, Jan 12, 2015 at 3:40 AM, Karl Dubost <karl@la-grange.net> wrote:
> I'm using multiple range selection very often. From every day to a couple of times a week. My main usage is when I use bookmarking services and I want to keep part of an article which are distant. Basically a "text1 […] text2 […] text3" scenario. I select when reading, and when finish I can bookmark all my selections in once. Also when I want to remove some noise from a paragraph.
> It's a lot more practical than having to create individual bookmark for each part OR to have to select, bookmark and cut.
> As a user I find that essential and very practical (implementation details apart).

I think the proposal for Gecko was to leave multiple-range selections
functional, but not expose anything beyond the primary range to author
JavaScript.  So there would be no change for users, only to authors.
Received on Monday, 12 January 2015 11:36:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:43 UTC