21430 2013-03-28 23:13:01 +0000 [Templates]: <template><table>Foo should result in <template> being the foster parent for "Foo" 2013-04-10 22:58:24 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 15476 1 rafaelw dglazkov adamk annevk dglazkov hsivonen ian tross wchen public-webapps-bugzilla oldest_to_newest 85132 0 rafaelw 2013-03-28 23:13:01 +0000 The spec says: "The foster parent element is the parent element of the last table element in the stack of open elements, if there is a table element and it has such a parent element." But the parent of the first table at this point will be the content document fragment. 85133 1 rafaelw 2013-03-28 23:24:39 +0000 Thinking about this more, I think it might be best to refactor the foster parent definition into an algorithm. The two changes to the existing logic that the template element spec requires are: 1) Don't foster parent elements outside the <template>, e.g. <body><table><template><tr><div> -<div> should be foster parented to the <template>, not above it) -this is currently covered in the template spec here: https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html#foster-parent-addition 2) Allow the <template> to be a foster parent, e.g. <template><table>Foo -What prevents this is that the <table>'s parent won't be an element. ---------- I'm not sure how to express the required changes to the existing spec text cleanly in the template element spec. Does anyone else think it's a good idea to create an algorithm here? 85186 2 annevk 2013-03-31 15:53:42 +0000 Can't we just change the text in HTML to say that if the parent is a <template>'s DocumentFragment, use that? For clarity defining the foster parent element as a list of steps might be good though. 85911 3 rafaelw 2013-04-10 22:58:24 +0000 Ok. Fixed. https://dvcs.w3.org/hg/webcomponents/rev/f2135772d3d4