W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > August 2012

[Bug 18729] [Custom]: instantiation algorithm omits creating shadow roots for custom base elements

From: <bugzilla@jessica.w3.org>
Date: Wed, 29 Aug 2012 18:04:17 +0000
Message-Id: <E1T6mcj-0003kx-1F@jessica.w3.org>
To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18729

--- Comment #3 from Scott Miles <sjmiles@chromium.org> 2012-08-29 18:04:16 UTC ---
(In reply to comment #2)
> (In reply to comment #1)
> > Recursive shadow-dom creation requires information about the extendee.
> > 
> > The section 4 algorithm takes only 'prototype' and 'template' inputs and it's
> > difficult to infer the extendee name from that input (it would require
> > searching the custom element registry for matching prototypes).
> > 
> > For our polyfill implementation we attached 'extendsName' to 'prototype' to get
> > around this problem.
> 
> Why not just use prototype.constructor?

I need to know if my prototype is derived from another custom element. I don't
see how prototype.constructor helps me find that information?

I suppose 'prototype.__proto__.constructor' might be the constructor I'm
looking for, but even then I need the Definition which contains the template
and I have no map of constructors to Definitions. 

Yes, we could make a map of constructors to Definitions, but it would require
Map support.

The simple registry maps tag-names to Definitions.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 29 August 2012 18:04:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 29 August 2012 18:04:18 GMT