W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: [css3-gcpm] maybe-floats vs "in-flow"

From: Håkon Wium Lie <howcome@opera.com>
Date: Thu, 16 Aug 2012 16:59:07 +0200
Message-ID: <20525.2747.745538.19687@gargle.gargle.HOWL>
To: Peter Moulder <peter.moulder@monash.edu>
Cc: www-style@w3.org
Also sprach Peter Moulder:

 > css3-gcpm introduces modifiers such as 'snap' or 'unless-room' for the
 > value of 'float' that can mean that the box isn't actually floated.


 > I wonder how this should interact with the various bits of CSS that make a
 > strong distinction between in-flow and out-of-flow boxes.  Some of these
 > decisions come quite early in the layout process, such as anonymous block
 > box generation.
 > The interaction as currently specified is that:
 >   # An element is called out of flow if it is floated [or ...].
 >   # An element is called in-flow if it is not out-of-flow.
 > I haven't thought much about how much of a problem this causes, but I am a
 > bit nervous about such foundations as initial box tree generation depending
 > on global layout choices.
 > I think that the spec should at least draw attention to this sort of
 > consequence of the float-or-in-flow decision for such a box.

Good point. How about saying that the element is considered to be a
float even when the condition doesn't apply? This will allow more
document processing to take place before laying out the document.

              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Thursday, 16 August 2012 14:59:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:20 UTC