W3C home > Mailing lists > Public > www-style@w3.org > October 2009

Re: Comments on css3-multicol

From: Giovanni Campagna <scampa.giovanni@gmail.com>
Date: Sun, 18 Oct 2009 15:50:35 +0200
Message-ID: <65307430910180650p679f0817xfb410652290a6f91@mail.gmail.com>
To: Håkon Wium Lie <howcome@opera.com>
Cc: www-style@w3.org
2009/10/18 Håkon Wium Lie <howcome@opera.com>

> Also sprach Giovanni Campagna:
>
>  > > Further, in the description of the "break" properties, this text now
>  > > occurs:
>  > >
>  > >  When a page or column break splits a box, the box's margins,
>  > >  borders, and padding have no visual effect where the split occurs.
>  > >  However, margins will be preserved after forced page/column break. A
>  > >  forced page/colum break is a break that does not occur naturally.
>  >
>  > Should you note "box-break"? There are UAs that may support
> css3-background
>  > before css3-multicol.
>
> Good point. I've changed the draft to:
>
>  When a page or column break splits a box, the box's margins,
>  borders, and padding have no visual effect where the split occurs.
>   However, the margin immediately after a forced page/column break
>  will be preserved. A forced page/colum break is a break that does
>  not occur naturally.
>
>  Note: In the future, new properties may describe alternate
>  ways to handle margins, borders and padding around page/column breaks.
>

Ok


>   > >   >     4.b) what happens if a non-floated element overflows
> vertically?
>  > >  > Is it still clipped regardless of overflow? Can implementations put
>  > >  > scrollbars, if overflow asks so?
>  > >
>  > > Yes, the spec states:
>  > >
>  > >  Content that extend outside column boxes at the edges of the
>  > >  multi-column element is clipped according to the 'overflow'
>  > >  property.
>  >
>  > There's still one problem. Consider:
>  >
>  > <div><img src="a"><img src="b"><img src="c"><img src="d"></div>
>  >
>  > div {
>  > column-count:3;
>  > column-fill:balance;
>  > height:300px;
>  > }
>  > img {
>  > height:300px;
>  > display:block;
>  > }
>  >
>  > Do I get 4 columns, one column longer than the other (overflowing), or
> two
>  > columns with two images each, and the third empty?
>
> The draft states:
>
>  A multi-column element can have more columns than it has room for due to:
>
>  - Constrained column height. The height can be constrained by a rule
>    on the multi-column element.
>
> This wording implies that the height should be honored and the number
> of columns increased. So, you would get 4 columns.
>
> However, the language is quite soft. Here's a stronger version:
>
>  A multi-column element can have more columns than it has room for due to:
>
>  - Constrained column height. A declaration that constrains the
>    column height (e.g., using 'height') must be honored, if possible.
>    In paged media, the column height is constrained by the size of
>    the page.
>
> I've added this to the editor's draft.
>

Good.


>
>  > Does it depend on overflow-x vs overflow-y on div?
>
> No. These properties specify what should happen when overflow occurs
> -- they should not influence which direction overflow takes.
>

Ok


>   > What if the images were always higher than the div's content area?
>
> Then you have overflow in the vertical direction. And the overflox*
> properties describe how to deal with it.
>

All right


>
>
Cheers,
>

Thanks for all explanations and time!


> -h&kon
>              Håkon Wium Lie                          CTO °þe®ª
> howcome@opera.com                  http://people.opera.com/howcome
>

Giovanni
Received on Sunday, 18 October 2009 13:51:08 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:21 GMT