16764 2012-04-17 23:40:29 +0000 [Shadow]: host attribute makes it hard to preserve encapsulation 2012-04-25 23:21:25 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 14978 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 66777 0 dominicc 2012-04-17 23:40:29 +0000 Take this use case: a component wants to provide a place for extension. For example, a video player may put playback controls in Shadow DOM but wants to let scripts add buttons to the controls. The component could do this: <!-- play/pause button --> <div id="extensionpoint"></div> and implement the extensionPoint attribute as: this.extensionPoint = new ShadowRoot(controls.querySelector('#extensionpoint')) Scripts can access the extensionPoint and add buttons to it, etc. However the component can’t preserve its own encapsulation, because the extensionPoint.host property will point into the component’s shadow. One way around this is for the component to do this: <!-- play/pause button --> <content select=".extensions"></content> And the caller writes: <…> <div class="extensions">…</div> … But it seems a shame that we lose the imperative API by having the "host" property. What is it good for? 67088 1 dglazkov 2012-04-25 23:19:10 +0000 Good use case. I will remove .host attribute. 67089 2 dglazkov 2012-04-25 23:21:25 +0000 http://dvcs.w3.org/hg/webcomponents/rev/57f8cfc4a7dc