W3C home > Mailing lists > Public > www-style@w3.org > June 2005

Re: Proposal: %% units

From: Andrew Fedoniouk <news@terrainformatica.com>
Date: Tue, 14 Jun 2005 19:58:18 -0700
Message-ID: <000801c57156$15a30ae0$3201a8c0@TERRA>
To: "Laurens Holst" <lholst@students.cs.uu.nl>
Cc: "Ben Curtis" <bcurtis@bivia.com>, <www-style@w3.org>

----- Original Message ----- 
From: "Laurens Holst" <lholst@students.cs.uu.nl>


> Andrew Fedoniouk wrote:
>
>> In fact any UA now has %% implemented internally.
>> At least table layout computation is using exactly the same or
>> very close principles. We don't need to invent anything major here
>> and to introduce new principles. Web designers already know
>> how to deal with them (in tables).
>
> If table layouts already implement this, then we don’t need %%, we can
> just use the CSS table properties.

Name 3 major differences in calculation of
<td width=50%>
and
<div style="display:table-cell; width :50%"/>
(I believe it is from second semester of Web Design course)

>
> The reason why tables work is that they have a strong structure of what
> contains what, and if two table-cells are in a table-row, then they will
> always be displayed next to eachother. Inline-block doesn’t have this, and
> it never will. You need another model for that, which I think will
> effectively mimick the table properties.

You don't need another model for that.
Proposed flow:horizontal (long time ago)
assumes height:auto for children - symmetric to
width: auto in flow:vertical .

>
>> Again, in my opinion,  calc makes sense when you will be able to do
>> following
>
> Calc doesn’t harm incremental reflow, because in the end they’re all
> constants just like they are now without calc().
>
>> img { float:left; margin:1em 1em 1em 0; width:120px; }
>> p { width:75%%; min-width:calc(#myimg.width + #myimg.margin[0] + 10em); }
>>
>> <img id="myimg" src="bio_pic.jpg" height="220" width="120" alt="" />
>> <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. ... </p>
>>
>> Otherwise you are getting redundant declarations. As you've mentioned
>> this is just not working for design in teams, etc.
>
> Working in teams is overrated. Seriously, at work, we work in a team.
> Multiple people are using and adapting the same stylesheet. I can assure
> you that there are aplenty of places in CSS where there is duplication of
> units and properties (just think of
> #a{float:left;width:100px}#b{padding-left: 100px} to create a column
> layout). No-one died, so to speak.

Sure.

PS: People here are pretty busy, try to reduce entropy in answers.

Andrew Fedoniouk.
http://terrainformatica.com
Received on Wednesday, 15 June 2005 02:56:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:37 GMT