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

Re: CSS: %% length unit. Proposal. Some clarifications.

From: Andrew Fedoniouk <news@terrainformatica.com>
Date: Sun, 9 May 2004 12:17:27 -0700
Message-ID: <004c01c435fa$448cf0c0$0301a8c0@ATHLON>
To: "Ian Hickson" <ian@hixie.ch>
Cc: <www-style@w3.org>
> > Right?
> No, with the table layout algorithm (as implemented by UAs) width:100%
> means "make this column as wide as possible given the constraints of the
> other columns".

Letter 's' in your 'UAs' is just mistyping I guess. Only Mozilla is trying to render them properly (from Mozilla point of of view).  
Yep, 'cause "given the constraints of the other columns" has strong smell of fuzzy logic.

> This is actually very poorly described by CSS2 right now, largely because
> nobody actually understands the table layout algorithm, which makes it one
> of the worst parts of CSS. Most implementations are developed by reverse
> engineering the more popular implementations.

In my opinion this happened because  table*-styles are "artificial" entities. Brave attempt to close holes. They conflict with e.g. box model. They create too many "if", "then", "except" across the whole specification.

Lack of  %% natural "fluid" mechanism in CSS was the main motivation to introduce them I guess.

> It's certainly a lot better than you have explained in the past. What do
> you mean by "line" exactly? Are floats and other overlapping elements part
> of the "line"? How do you determine what is on a line? What if there is no
> line box?

Exactly as it is right now. "Line" means "line box", floats if exist constitute left/right margins of the line box.

> What if the container width is less than the width of the word "from:"?

They will wrap as words.

Follow INPUTS on the first line :
Width #1

Width #2

Width# 3

Floaters/ left side:


Floaters/ both sides:

Andrew Fedoniouk.

Received on Sunday, 9 May 2004 15:27:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:13 UTC