W3C home > Mailing lists > Public > www-style@w3.org > May 2013

Re: [css3-multicol] Re: [CSSWG] Minutes Telecon 2013-05-01

From: Håkon Wium Lie <howcome@opera.com>
Date: Sat, 4 May 2013 20:20:42 +0200
Message-ID: <20869.20858.190445.733135@gargle.gargle.HOWL>
To: Simon Sapin <simon.sapin@exyr.org>
Cc: François REMY <francois.remy.dev@outlook.com>, www-style@w3.org
Also sprach Simon Sapin:

 > > I support this resolution; we shouldn't try to solve this in the
 > > multicol spec.
 > 
 > I agree (fragmentation details go in the Fragmentation spec), but this 
 > only one half of issue originally reported by François. The other half 
 > is overflow in the inline dimension of out-of-flow elements, and I think 
 > the spec should add something there:
 > 
 > >    - Discussed issues with overflowing floats in multicol
 > >       http://lists.w3.org/Archives/Public/www-style/2013Apr/0639.html

And, in another message:

 > "In-flow" is defined in CSS 2.1 and clearly does not apply to floated 
 > elements. But we could could change the spec to say "Floated or in-flow 
 > content that extends …"
 > 
 > http://www.w3.org/TR/CSS21/visuren.html#x24

The proposal is then to change this sentence:

  Content in the normal flow that extends into column gaps (e.g., long
  words or images) is clipped in the middle of the column gap.

  http://www.w3.org/TR/css3-multicol/#overflow

to 

  Floated or in-flow content that extends into column gaps (e.g., long
  words or images) is clipped in the middle of the column gap.

This makes sense to me; I kinda think of floats as being in the flow
(although pushed to the side of the river, it's not airlifted away
like abspos) and it makes sense to treat them like in-flow content.

Any objections?

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Saturday, 4 May 2013 18:21:18 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 4 May 2013 18:21:19 UTC