- From: Tim Down <tim@timdown.co.uk>
- Date: Wed, 7 Jan 2015 00:02:41 +0000
- To: Ryosuke Niwa <rniwa@apple.com>
- Cc: Webapps WG <public-webapps@w3.org>
Received on Wednesday, 7 January 2015 00:03:09 UTC
For what it's worth as a user of the range and selection APIs, updating a live range is convenient and preferable, but since this has never worked in all browsers, I never do it and have never recommended it to anyone else. Therefore if Gecko changes, nothing really changes for me, so I don't care. Knock yourself out, Mozilla. Tim On 6 January 2015 at 22:32, Ryosuke Niwa <rniwa@apple.com> wrote: > https://github.com/w3c/selection-api/issues/40 > > Trident (since IE10) and Gecko both return a live Range, which can be > modified to update selection. WebKit and Blink both return a clone Range > so that any changes to the Range doesn't update the selection. > > It appears that there is a moderate interest at Mozilla to change Gecko's > behavior. Does anyone have a strong opinion about this? > > - R. Niwa > > >
Received on Wednesday, 7 January 2015 00:03:09 UTC