- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 8 Apr 2013 11:52:48 -0700
- To: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
- Cc: "www-style@w3.org" <www-style@w3.org>
On Mon, Apr 8, 2013 at 10:54 AM, Rossen Atanassov <Rossen.Atanassov@microsoft.com> wrote: > As specified the current 'flow-into' property takes an element out of its flow and places it into a flow with a given 'ident'. However, there are use cases where the element is not needed as part of the redirected flow but its content only. I'm proposing that we achieve this by extending the current '<ident>' value with an additional, conditional 'content-only' value. In other words, the 'flow-into' property values will be changed to: [<ident> content-only?] | none | inherit. > > One more aspect which is worth nothing here is that keeping the behavior mutually exclusive will result in less confusion - you either get the element or its content. Otherwise I can see cases where the element is placed in a flow A and then a different rule places its content into a flow B... would flow A have the element only or its content duplicated as well etc..? Alternately, rather than special-casing Regions here, we can just use the "display-box: contents" value in the Display draft. Same effect, but more general. ~TJ
Received on Monday, 8 April 2013 18:53:39 UTC