- From: Jonas Sicking <jonas@sicking.cc>
- Date: Thu, 17 Oct 2013 11:56:03 -0700
- To: Hajime Morrita <morrita@google.com>
- Cc: Ryosuke Niwa <rniwa@apple.com>, Sudarshan <sudarshan.p@samsung.com>, Webapps WG <public-webapps@w3.org>
On Thu, Oct 17, 2013 at 1:55 AM, Hajime Morrita <morrita@google.com> wrote: > > > > On Thu, Oct 17, 2013 at 5:01 PM, Ryosuke Niwa <rniwa@apple.com> wrote: >> >> On Oct 16, 2013, at 9:47 PM, Hajime Morrita <morrita@google.com> wrote: >> >> D. "H[ello Shado]w World" - selection spans outside to inside. >> >> >> Suppose we allowed this selection. Then how does one go about pasting this >> content elsewhere? >> >> Most likely, whatever other content editable area, mail client, or some >> random app (e.g. MS Word) into which the user is going to paste wouldn’t >> support shadow DOM and most certainly wouldn’t have the component the >> original page happened to have. > > > We have to define how Range.cloneContents() or extractContents() works > against shadow-selecting range, assuming selection is built on top of DOM > Range. This doesn't seem that complicated. As cloned element drops its > shadow, these range-generated nodes won't have shadow either. Oh, sounds like you are suggesting that we expand the Range API such that it can have awareness of spanning parts of a shadow DOM tree. While still keeping the existing endpoints "in the same root"? That like that idea! 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. / Jonas
Received on Thursday, 17 October 2013 18:57:01 UTC