- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 9 Sep 2015 10:12:36 +0200
- To: Hayato Ito <hayato@google.com>
- Cc: public-webapps <public-webapps@w3.org>, Ian Hickson <ian@hixie.ch>
On Mon, Sep 7, 2015 at 9:35 AM, Hayato Ito <hayato@google.com> wrote: > I think the spec should address these issues and define the well-defined > behavior clearly. The current spec looks too lazy because it only mention > the following: > >> Window object named properties [HTML] must access the nodes in the >> document tree. > > I think this is not enough to achieve the interoperability among UAs. Right, for many HTML features this seems problematic. Are you planning on working on this and provide patches against https://github.com/whatwg/html? If you think this is too much work let me know and I'll see what I can to help. I'm trying to decrease the backlog of HTML somewhat so this is not currently a priority for me, but it is one of the things Mozilla considers problematic with shipping Shadow DOM at this point. >> Then there's the matter of text selection which we're not sure about >> what to do. Have you folks worked on that? > > I've discussed this topic several times in Google, however, this is still an > unsolved problem. > We don't have anything which we can upstream to the spec yet. > In Blink, we've supported only "Copy" for a selection which spans shadow > boundaries. > Any ideas are highly welcome. Given that https://w3c.github.io/selection-api/ is edited by Ryosuke, I wonder what his thoughts are. This issue must not have gotten past the Apple team. At Mozilla we don't have a concrete proposal, it's however something we don't think works well currently and we don't really know how to move forward here. -- https://annevankesteren.nl/
Received on Wednesday, 9 September 2015 08:13:08 UTC