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 15858 - Should first region be ICB for flow content?
Summary: Should first region be ICB for flow content?
Alias: None
Product: CSS
Classification: Unclassified
Component: Fragmentation (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: fantasai
QA Contact: public-css-bugzilla
Whiteboard: model
Depends on:
Reported: 2012-02-02 21:48 UTC by Alex Mogilevsky
Modified: 2012-04-12 19:39 UTC (History)
3 users (show)

See Also:


Description Alex Mogilevsky 2012-02-02 21:48:39 UTC

Absolute positioning in fragmented flow in general should be defined outside regions spec (css3-fragmentation I would assume).

Whether or not first region is ICB for named flow content (and therefore positioned content is constrained to regions) or not - that deserves a separate decision, which to me seems related to stacking context decision.

My opinion: if stacking context for region is to be made optional (especially to allow matching stacking behavior of columns), constraining of positioning to regions will have to be optional for the same reason.
Comment 2 Edward O'Connor 2012-02-07 22:50:23 UTC
See also Hyatt's explanation of WebKit's implementation in
Comment 3 Vincent Hardy 2012-04-12 19:39:02 UTC
Moved to fragmentation spec. following Paris F2F discussion and Action Item