W3C home > Mailing lists > Public > public-css-bugzilla@w3.org > February 2012

[Bug 16002] New: flow-into and anonymous blocks or fix-ups

From: <bugzilla@jessica.w3.org>
Date: Thu, 16 Feb 2012 17:10:26 +0000
To: public-css-bugzilla@w3.org
Message-ID: <bug-16002-5148@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16002

           Summary: flow-into and anonymous blocks or fix-ups
           Product: CSS
           Version: unspecified
          Platform: PC
               URL: http://lists.w3.org/Archives/Public/www-style/2012Feb/
                    0733.html
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Regions
        AssignedTo: vhardy@adobe.com
        ReportedBy: vhardy@adobe.com
         QAContact: public-css-bugzilla@w3.org
                CC: eoconnor@apple.com


>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)?

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 16 February 2012 17:10:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 16 February 2012 17:10:35 GMT