18753 2012-08-31 20:21:35 +0000 [Shadow]: Introduce HTMLContentElement projection API 2014-02-11 18:45:24 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED INVALID P2 normal --- 18429 1 dglazkov dglazkov morrita public-webapps-bugzilla oldest_to_newest 73106 0 dglazkov 2012-08-31 20:21:35 +0000 Expose DOM API on HTMLContentElement to explicitly add/remove nodes to be projected into it. 73120 1 dglazkov 2012-08-31 22:43:09 +0000 NodeList HTMLContentElements.distributed if you add an item to distributed that is already in the distributed of a younger tree or higher in tree, it is not rendered (render only once). How is this accomplished? The rendering algo could account for things that have already been rendered, thus letting duplicate items be stored in the various insertion points' distributions. However, the problem here is that now you have no idea (looking at the insertion point) whether any given item renders or not. Thus, we have to eject or reject items added to "distributed". In case of "first one wins", we reject additions (throw exception?) In case of "last one wins", we eject previously added items (event?) 76467 2 morrita 2012-10-17 04:47:04 +0000 Is the list dynamic or static? If it is a static list, it's better to make this a method instead of attribute. I don't think attribute + static list follows Web API norm. 100306 3 dglazkov 2014-02-11 18:45:24 +0000 These are old ideas that haven't panned out.