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

RE: [css3-multicol] new editor's draft

From: Shelby Moore <shelby@coolpage.com>
Date: Tue, 26 Oct 2010 20:44:12 -0400
Message-ID: <279ce7253030d424e27aec4c637dfb9b.squirrel@sm.webmail.pair.com>
To: "Sylvain Galineau" <sylvaing@microsoft.com>
Cc: "Håkon Wium Lie" <howcome@opera.com>, "Alex Mogilevsky" <alexmog@microsoft.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "www-style@w3.org" <www-style@w3.org>
Sylvain Galineau wrote:
>> From: Shelby Moore
>> So in my and I think the designer's mind, the correct result is:
>> Inline overflow:
>>  baz----------------------->
>>  foo | foo | foo | bar | qux
>> Block overflow:
>>  baz------------->
>>  foo | foo | foo |
>>  bar | qux
>> Now isn't that a lot more sane and consist?

Typo, 'consist' -> 'consistent'.

> I sure don't know since I can't tell what your answer is. I see two
> different
> renderings ?

One is for when overflow is in the inline direction, and the other is for
when overflow is in the block direction.  Currently the spec only allows
overflow in the inline direction, but I assume the spec will be
generalized in the future, so I showed both cases.

> I'll assume, however, that in both cases you layout baz on top of all the
> columns.

Note I had an error for the block overflow case, and I was writing my
correction while you were replying:


Actually it needs to be corrected more, as baz should only span the 2
columns in the new column row:

Block overflow:
 foo | foo | foo
 bar | qux

> How and why does is that correct per the designer's mind ? Why would he
> expect all
> the other elements to flow in source order except that one ?

The spanned element is also flowing in source order.

Pehaps what is confusing is in general foo, bar, and qux be spannable lines.

Let's assume instead with monospace font:

foo = fff ooo
bar = bbb arr
qux = qqq uxx

Inline overflow:
 fff | fff | fff | bbb | qqq
 ooo | ooo | ooo | arr | uxx

Block overflow:
 fff | fff | fff
 ooo | ooo | ooo
 bbb | qqq
 arr | uxx

Now assume bar = bar and is before baz.

Inline overflow:
 fff | fff | fff | bar | uxx
 ooo | ooo | ooo | qqq

Block overflow:
 fff | fff | fff
 ooo | ooo | ooo
 bar | uxx

>> Note it is incorrect to assume baz is centered,
>> that is why I drew it
>> as I
>> did on the left side with an arrow showing its extent.
> Uh ? The element's style attribute says text-align:center.

I must have lost that from the original example. Apologies. Then yes it
should be centered. In any case, I am adding the arrow to show the precise
extent of the span.

> How do we
> ignore
> properties explicitly specified by the designer and claim the result
> aligns
> with his expectations ?

I would not argue for that. Was merely not seeing the center attribute.
Let's try to keep examples simple, not need to include an extraneous
center attribute as it is not germane/relevant to this. Sorry I just
missed it.
Received on Wednesday, 27 October 2010 00:44:38 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:40 UTC