W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [Component Model]: Shadow DOM Subtree per element: One or Many?

From: Roland Steiner <rolandsteiner@google.com>
Date: Fri, 26 Aug 2011 16:24:27 +0900
Message-ID: <CACFPSphaK5+CS-HpUL16207Go8c_TukxEXXu4aO6gu+3kd+c0A@mail.gmail.com>
To: Dominic Cooney <dominicc@google.com>
Cc: Dimitri Glazkov <dglazkov@chromium.org>, Erik Arvidsson <arv@chromium.org>, public-webapps <public-webapps@w3.org>, Adam Barth <w3c@adambarth.com>, Alex Russell <slightlyoff@google.com>, MarkM Miller <erights@google.com>
Unless I'm misunderstanding something, I believe this actually is - or at
least touches upon - several questions in disguise:

.) Do we want to allow decoration of elements that are already in the DOM
tree?

- which is for all intents and purposes a corollary of:

.) Do we allow calling of "new ShadowRoot" outside of an element
constructor?

If no, then we don't have a problem with "dead elements", because the author
can only declare new elements (and use encapsulation), but not meddle with
existing ones. FWIW, I don't think there is any real use-case for calling
"new ShadowRoot" within the constructor twice.
However, in this case we have to answer how encapsulation can address the
stated use cases for decoration. This probably means answering:

.) How is attribute forwarding handled from the host element to a nested
(form) element?
.) How can components participate in forms (and other fun)?

... or just leave decoration out for the time being (which I think is quite
reasonable).

OTOH, if the answer to the decorators question is "yes", then the above
mentioned issues with multiple shadow roots arise.
Received on Friday, 26 August 2011 07:25:12 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT