This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16002 - flow-into and anonymous blocks or fix-ups
Summary: flow-into and anonymous blocks or fix-ups
Alias: None
Product: CSS
Classification: Unclassified
Component: Regions (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Vincent Hardy
QA Contact: public-css-bugzilla
Depends on:
Reported: 2012-02-16 17:10 UTC by Vincent Hardy
Modified: 2012-10-02 21:26 UTC (History)
2 users (show)

See Also:


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;}

What you get in the named flow is actually


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