[webkit-dev] Shadow DOM API (first iteration) ready for landing

Dimitri Glazkov dglazkov at chromium.org
Thu Jun 30 13:21:09 PDT 2011

Hi Sam!

On Wed, Jun 29, 2011 at 7:50 PM, Sam Weinig <weinig at apple.com> wrote:
> Hi Dimitri,
> First of all, nice work on getting to this point!

Thanks, it's been a nice, long slog :)

> It is not clear to me why we wouldn't stick with XBL2 for now, at least until there is more community consensus on going another way, and a spec and editor are available to take the API forward.  I think it would help if you could explain what considerations you took into account when making this decision, and further, why this subset is a good starting place. What are the use cases of this subset?

I think you're right, more work is needed in getting more consensus on
the first step. I am glad this thread generated so much excitement,
even if mixed with confusion. As a result, we've taken this thread to
public-webapps. Maciej is asking exactly the same questions here:

Please follow along :)


> - Sam
> On Jun 28, 2011, at 7:42 PM, Dimitri Glazkov wrote:
>> Dear WebKit,
>> After nearly a year of building up the shadow DOM plumbing and
>> converting WebKit to use it, we are finally at the point where we can
>> expose this plumbing as public-facing API. The approach we take here
>> is a very cautious one: we want to expose the minimum subset of the
>> larger Web Component Model (some of you might remember is it as XBL2).
>> The goal is to minimize the impact, but have something useful enough
>> for Web developers to help us gather feedback.
>> After careful consideration, we've come up with this subset for our
>> first iteration:
>> http://dglazkov.github.com/component-model/dom.html
>> Since this is an experimental API, here are the actual API names we want to use:
>> Element.webkitShadow
>> Element.webkitPseudo
>> document.webkitCreateShadow()
>> window.WebKitShadowRootConstructor
>> window.WebKitTreeScopeConstructor
>> We will also provide the ENABLE(COMPONENT_MODEL) flag to control
>> availability of this API and its iterations, even though all of the
>> C++ code will always compile, since it's used throughout WebKit.
>> NOTE: This iteration of the API is not intended to ship in a release
>> version of a browser (think nightlies and dev channel only). Be sure
>> to disable it on your respective release branches.
>> Please chime in if you have concerns. Wish us luck!
>> :DG<
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

More information about the webkit-dev mailing list