- From: <bugzilla@jessica.w3.org>
- Date: Thu, 28 Mar 2013 23:24:39 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21430 --- Comment #1 from Rafael Weinstein <rafaelw@chromium.org> --- 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? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 28 March 2013 23:24:41 UTC