- From: Travis Leithead <travis.leithead@microsoft.com>
- Date: Thu, 17 Oct 2013 19:24:01 +0000
- To: Jonas Sicking <jonas@sicking.cc>, Hajime Morrita <morrita@google.com>
- CC: Ryosuke Niwa <rniwa@apple.com>, Sudarshan <sudarshan.p@samsung.com>, Webapps WG <public-webapps@w3.org>
From: Jonas Sicking [mailto:jonas@sicking.cc] > Though I'd also be interested to hear how other implementations feel about the Gecko solution of allowing selection to be comprised of multiple DOM Ranges. Seems totally reasonable; only problem is that pretty much all content on the web assumes one range per selection: getSelection().getRangeAt(0); and this programmatic selection-extraction would miss part of the selection if it were broken up. Ideally not the what that code should be doing, but since user-multi-selection isn't interoperable, there's no critical mass to change this practice, in practice.
Received on Thursday, 17 October 2013 19:24:32 UTC