15589 2012-01-17 02:41:40 +0000 [Shadow]: Content element should be able to specify a parser context for fallback content, and allowed in many (any?) contexts 2012-01-18 18:49:15 +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 62800 0 dominicc 2012-01-17 02:41:40 +0000 The content element may be used to provide fallback content in various contexts, for example, by providing rows in a table: <table> <content select="tr"> <tr> … </tr> </content> </table> Should the content model of all? almost all? elements be extended to permit the content element? Should the content element be able to specify its content model (perhaps by analogy to another element; in the above example as table?) 62819 1 dglazkov 2012-01-17 21:44:33 +0000 Note to self: this is going to be the same set of content model modifications as for HTML Templates. 62821 2 dglazkov 2012-01-17 23:53:37 +0000 I believe this is the Transparent content model: http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#transparent What do you think? 62823 3 dglazkov 2012-01-18 00:25:04 +0000 http://dvcs.w3.org/hg/webcomponents/rev/6d61186d429e WDYT? 62834 4 dominicc 2012-01-18 02:18:17 +0000 Transparent content model is splendid for the content element’s content model. There is still the problem of allowing content element everywhere. The transparent content model doesn’t affect where the element with the transparent content model can appear, does it? For example we still have this problem: <table> <content> <tr> <td>foo</td> </tr> </content> </table> will be parsed as something like <table> <content></content> <tbody> <tr> <td>foo</td> </tr> </tbody> </table> ? 62836 5 dglazkov 2012-01-18 03:25:43 +0000 (In reply to comment #4) > Transparent content model is splendid for the content element’s content model. > > There is still the problem of allowing content element everywhere. The > transparent content model doesn’t affect where the element with the transparent > content model can appear, does it? For example we still have this problem: > > <table> > <content> > <tr> > <td>foo</td> > </tr> > </content> > </table> > > will be parsed as something like > > <table> > <content></content> > <tbody> > <tr> > <td>foo</td> > </tr> > </tbody> > </table> > > ? That's just hard-coded into the parser: http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#parsing-main-intable As far as I understand, content models aren't related back into the parser. They are just semantic glitter. 62868 6 dglazkov 2012-01-18 18:49:15 +0000 I am going to close this and open parser changes bug separately.