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

Re: [CSS3] Some thoughts about 'display-model' property

From: Andrew Fedoniouk <news@terrainformatica.com>
Date: Fri, 24 Dec 2004 19:18:33 -0800
Message-ID: <000801c4ea30$6a5a9e70$0c01a8c0@TERRA>
To: "Orion Adrian" <orion.adrian@gmail.com>, <www-style@w3.org>

And one more to this subject:

It would be nice to add to
'display-role' list of values also 'body' or 'content'

Having this will allow to set
window/view scrollbars to reflect scroll position of such element.

I would like to see also sort of <content> tag in HTML for that or
to allow decoration markup (menus, sidebars, etc) be outside <BODY>
element. In this case it will be easier to access/find real content of the 
page
for non visual UA's.

Therefore if  'display-model' of the main container of the page will be
set to something like 'border-layout' and central
element will be set to display-role: body
we will have flexible full view layout and
view scrollbars reflecting content area.

Andrew Fedoniouk.
http://terrainformatica.com


Original Message from: "Orion Adrian" <orion.adrian@gmail.com>
To: <www-style@w3.org>
Sent: Thursday, December 23, 2004 6:20 PM
Subject: Re: [CSS3] Some thoughts about 'display-model' property


|
| This I could seriously get behind. I'd like to see more comments on
| this from the list. Any thoughts?
|
|
| On Tue, 21 Dec 2004 12:32:30 -0800, Andrew Fedoniouk
| <news@terrainformatica.com> wrote:
| >
| > 'display', 'display-model' and 'display-role' attributes (or 
properties?)
| > are defined in [1]
| >
| > I think that separation of 'display-model' and 'display-role'
| > is very reasonable.
| >
| > My understanding of 'display-model' and 'orientations of flows'
| > is as such:
| >
| > 'display-model' defines layout behavior of all normal(natural)
| > flow elements in the container.
| >
| > It is a bit different from "The 'display-model' property
| > determines the algorithm with which an element lays
| > out its children" as absolute positioned children are
| > not affected by container's 'display-model'. (I hope)
| >
| > Second thought is more radical I would say:
| >
| > 'display-model' is in fact a definition of a layout manager
| > algorithm used by a container.
| > Layout managers, as an entity, is well known and time proven
| > concept in Java world (and not only in Java).
| > Standard list of Java layout managers could be
| > found here [2].
| >
| > I think that CSS will benefit if it would be possible to say
| > e.g. display-model:border-layout or display-model:grid-layout
| >
| > In fact current definition of display::table in CSS is just rudimental
| > Java::GridLayout.
| > But HTML::<TABLE> element has what Java uses as a Java::GridBagLayout.
| >
| > I guess that if we will modify display-model list of values as
| >
| > inline-layout
| > block-layout (or box-layout)  - standard layout for DIV container
| > border-layout
| > flow-layout  - all children are inline-blocks
| > grid-layout
| > grid-bag-layout
| > card-layout (probably)
| > spring-layout (probably)
| >
| > it will increase usability and clearness of CSS a lot.
| > Clearly defined, time proven and familiar concept.
| >
| > --------------------------------------------
| > [1] http://w3.org/TR/2002/WD-css3-box-20021024/#L706
| > [2] http://java.sun.com/docs/books/tutorial/uiswing/layout/visual.html
| >
| > Thanks.
| >
| > Andrew Fedoniouk.
| > http://terrainformatica.com
| >
| >
| 
Received on Saturday, 25 December 2004 03:18:49 GMT

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