RE: [Selection] Should selection.getRangeAt return a clone or a reference? from Ben Peters on 2015-01-06 (public-webapps@w3.org from January to March 2015)

From: Ben Peters <Ben.Peters@microsoft.com>
Date: Tue, 6 Jan 2015 22:39:39 +0000
To: Ryosuke Niwa <rniwa@apple.com>, Webapps WG <public-webapps@w3.org>
Message-ID: <BLUPR03MB437E7C21FE596D82F36E91F83590@BLUPR03MB437.namprd03.prod.outlook.com>

I'm not sure if any sites depend on the Gecko/Trident behavior, but I imagine any such sites also work in Webkit/Blink. So I'm fine with changing this unless anyone knows of an important dependency.

-----Original Message-----
From: Ryosuke Niwa [mailto:rniwa@apple.com] 
Sent: Tuesday, January 6, 2015 2:32 PM
To: Webapps WG
Subject: [Selection] Should selection.getRangeAt return a clone or a reference?

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 Tuesday, 6 January 2015 22:40:07 UTC