W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: Mozilla and the Shadow DOM

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 16 Apr 2015 05:45:29 +0200
Message-ID: <CADnb78jrAoZP29wceX7UY=tK5siFMYXfTcsY4MdTrZbMxNbdJw@mail.gmail.com>
To: Elliott Sprehn <esprehn@chromium.org>
Cc: WebApps WG <public-webapps@w3.org>, Wilson Page <wilsonpage@me.com>
On Thu, Apr 16, 2015 at 2:41 AM, Elliott Sprehn <esprehn@chromium.org> wrote:
> I don't think you need to duplicate anything. The super class can still fill
> in the original shadow root, then the subclass can modify it. This is the
> same concept of the prototype inheritance, your methods will shadow the
> super class methods, but you can just call them and then extend the
> behavior.

In this case the subclass would have to poke into the superclass'
shadow DOM. If at any point those writing the superclass decide to
change the structure of that DOM they might end up breaking a subclass
they had no knowledge of. Allowing insertion of the whole shadow DOM
allows for changes that have fewer side effects.

Having said that, if your comment means that Google is no longer
interested in keeping this, we can probably be persuaded to keep this
out of a cross-browser v1 of shadow DOM.

Received on Thursday, 16 April 2015 03:45:58 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC