W3C home > Mailing lists > Public > public-css-testsuite@w3.org > September 2013

Re: [css3-multicol] multicol-span-all-child-002 review: proposed replacement

From: Håkon Wium Lie <howcome@opera.com>
Date: Sun, 1 Sep 2013 18:21:05 +0200
Message-ID: <21027.26993.641797.299117@gargle.gargle.HOWL>
To: =?iso-8859-1?Q?"G\=E9rard\?\= Talbot" <css21testsuite@gtalbot.org>
Cc: "Public css-testsuite mailing list" <public-css-testsuite@w3.org>
Also sprach "Gérard Talbot":

 > > Small point: perhaps we should replace the lime background with a white
 > > background (in case somone tries to print these documents :)
 > 
 > I agree.
 > 
 > I just changed lime for white in the test and then white for black.

Good.

 > > I'm a little unsure what the test tries to do. It's clear that the <div>
 > > element is too big to fit, and that implementations *may* therefore
 > > ignore 'column-span: all'. In which case, the <div> is laid out in two
 > > columns. If so, however, how can you fit three of the <span> elements in
 > > the first column?
 > 
 > The <span> color is black but its background is transparent. And there
 > is a soft (unforced) column break affecting the 3rd <span> element. The
 > 3rd <span> element is broken across 2 column boxes.

Implementations may treat the <span> as unbreakable, I believe.
Probably not a good idea, but not illegal, either -- and in any case
not something we should test here.

 > > The height of the div is 10em, and each span is 4em
 > > high. Shouldn't there only be four <span> elements, two for each column?
 > 
 > 4 <span> elements instead of 5 will also work. But 5 <span> elements
 > should also work.

So I suggest reducing the elements to 4.

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Sunday, 1 September 2013 16:21:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 20 January 2023 19:58:19 UTC