- From: Mihai Balan <mibalan@adobe.com>
- Date: Wed, 6 Nov 2013 17:39:09 +0000
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: WWW Style <www-style@w3.org>
Now that you spell it this way, it seems it was already in the spec[1] :) What about a float overflowing a (last) region with a fixed size? Would the float in this case interact with non flowed, non-float content? [1] http://www.w3.org/TR/css3-regions/#flow-from the text after the second note On 11/6/13 7:21 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote: >On Wed, Nov 6, 2013 at 9:06 AM, Mihai Balan <mibalan@adobe.com> wrote: >> Hello everybody, >> I'd like to know your position on the following scenario: suppose we >>have >> some content that gets flowed in an auto-sized region, and said content >>also >> has a floated box in it, that's taller than the non-float content. >>Should >> the size of the region be the size of the non-float *and* float content >> (taller) or just the size of the non-float content (shorter)? >> >> A corollary to this scenario is what should the size for an auto-size >>region >> when the only thing flowed in it would be a float? >> >> My personal take is that the float itself should not contribute to the >> sizing of the regions other than through the eventual shortening of line >> boxes of the surrounding contents and/or clearing. (The answer to the >> corollary being that the region should have 0 height). > >This tends to be a pretty undesirable behavior for people. They want >their elements that are semantically "containers" to contain floats, >and do a bunch of hacks to make it happen. I'd be much more in favor >of having the region container act like a BFC in this case. > >~TJ
Received on Wednesday, 6 November 2013 17:40:35 UTC