18842 2012-09-11 23:53:39 +0000 [Custom]: Custom element instantiation creates older ShadowRoots for more derived types, which is counterintuitive 2012-10-24 20:03:12 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 17103 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 73652 0 dominicc 2012-09-11 23:53:39 +0000 Custom element instantiation processes a custom element’s prototype chain "in reverse order (starting with the most-derived object)". This means in step 4.4.2, that more derived custom elements create their ShadowRoot first. This has the effect of masking their ShadowRoot with less-derived custom elements, which is counter-intuitive. For example, given: <element name="x-happy-button" extends="button"> <template> <img src="balloons.gif"> <content></content> <img src="clowns.gif"> </template> </element> <element name="x-super-happy-button" extends="x-happy-button"> <template> <div style="width: 500px; height: 500px; background: teal;"> <img src="stars.gif"> <shadow></shadow> <img src="puppies.gif"> </div> </template> </element> then <x-super-happy-button>Hello!</x-super-happy-button> will not be big, teal, nor have stars nor puppies, because the super happy ShadowRoot content will have been preempted by the younger, merely happy ShadowRoot which was instantiated later. 77064 1 dglazkov 2012-10-24 20:03:12 +0000 http://dvcs.w3.org/hg/webcomponents/rev/632c44aed726 Sorry, I misunderstood the meaning of "most-derived" to mean the opposite :)