Bug 16002 - flow-into and anonymous blocks or fix-ups
flow-into and anonymous blocks or fix-ups
Status: RESOLVED FIXED
Product: CSS
Classification: Unclassified
Component: Regions
unspecified
PC All
: P2 normal
: ---
Assigned To: Vincent Hardy
public-css-bugzilla
http://lists.w3.org/Archives/Public/w...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-16 17:10 UTC by Vincent Hardy
Modified: 2012-10-02 21:26 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Hardy 2012-02-16 17:10:25 UTC
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)?
Comment 1 Alan Stearns 2012-10-02 00:58:17 UTC
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"
Comment 2 Alan Stearns 2012-10-02 21:26:22 UTC
Fixed in https://dvcs.w3.org/hg/csswg/rev/b76903becabe