16002 2012-02-16 17:10:25 +0000 flow-into and anonymous blocks or fix-ups 2012-10-02 21:26:22 +0000 1 1 1 Unclassified CSS Regions unspecified PC All RESOLVED FIXED http://lists.w3.org/Archives/Public/www-style/2012Feb/0733.html P2 normal --- 1 vhardy vhardy eoconnor stearns public-css-bugzilla oldest_to_newest 64175 0 vhardy 2012-02-16 17:10:25 +0000 From the original email message [css3-regions] flow-into on inline or table-cell: The spec says 'flow-into' applies to anything. If applied to inline elements, what are expectations for flow behavior - are inline elements concatenated in lines, or should there be an anonymous block for each one? Also, if elements in flow are of the kind that normally require fixup (like table-cell), is it expected that fixup is performed separately in the composed flow, or would such elements change effective display type (e.g. table-cell would become a block unless it somehow ends up in a table-row)? 75014 1 stearns 2012-10-02 00:58:17 +0000 One thing we should point out is that the elements in the named flow have no whitespace separation. So if you have something like this: span {flow-into:named-flow;} <span>one</span> <span>two</span> What you get in the named flow is actually <span>one</span><span>two</span> So by moving the span elements from their markup parent (that contains the whitespace) you're changing what gets displayed from "one two" to "onetwo" 75117 2 stearns 2012-10-02 21:26:22 +0000 Fixed in https://dvcs.w3.org/hg/csswg/rev/b76903becabe