- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Sat, 5 Sep 2015 17:53:56 +0200
- To: Hayato Ito <hayato@google.com>
- Cc: public-webapps <public-webapps@w3.org>, Ian Hickson <ian@hixie.ch>
On Fri, Aug 28, 2015 at 8:33 AM, Hayato Ito <hayato@google.com> wrote: > - Some of the remaining issues are difficult to address in the Shadow DOM > spec because it requires non-trivial monkey patches to DOM. I have a plan > to upstream the Shadow DOM spec into DOM in the near future. After that, I > think we can address some of issues by updating DOM spec directly. That sounds great! It also seems there's still a number of issues around integration with HTML. That is, what the effect of HTML elements should be inside shadow trees. I seem to remember Ian having more detailed notes, but quickly looking around I only found: * https://www.w3.org/Bugs/Public/show_bug.cgi?id=27406 * https://www.w3.org/Bugs/Public/show_bug.cgi?id=26952 * https://www.w3.org/Bugs/Public/show_bug.cgi?id=28748 And these don't seem to mention the effects of various algorithms. E.g., named access on the global object currently finds child browsing contexts, but I don't think we would want it to return any that are inside a shadow tree. And should browsing contexts inside shadow trees have an effect on history? Then there's the matter of text selection which we're not sure about what to do. Have you folks worked on that? -- https://annevankesteren.nl/
Received on Saturday, 5 September 2015 15:54:19 UTC