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

Re: Positioned Layout proposal

From: Andrew Fedoniouk <andrew.fedoniouk@live.com>
Date: Fri, 22 Oct 2010 19:52:52 -0700
Message-ID: <bay141-DS16B6F46D0D010230E7F227F85F0@phx.gbl>
To: <shelby@coolpage.com>, "Boris Zbarsky" <bzbarsky@MIT.EDU>
Cc: "www-style list" <www-style@w3.org>
From: "Shelby Moore" <shelby@coolpage.com>
Sent: Friday, October 22, 2010 5:05 AM
To: "Boris Zbarsky" <bzbarsky@MIT.EDU>
Cc: "www-style list" <www-style@w3.org>
Subject: Re: Positioned Layout proposal

>> On 10/21/10 3:35 PM, Shelby Moore wrote:
>>> Those 1000s of elems on page are mostly inline content.
>> In the cases that worry me, they're mostly absolutely positioned,
>> floated, table cells, blocks, etc.
> Well if they are absolutely positioned, then there is much less of a
> constraint to solve. Tables cells is a repeating structure with a defined
> semantics.
> I am also skeptical as to whether we can generalize, maintain performance
> and avoid nasty circularity errors. So I wouldn't dare propose something
> for implementation which wasn't well understood by that time. So please do
> not be concerned that I am trying to shove some insane thing down the
> implementor's throats (I couldn't any way obviously).
> Perhaps I can allocate more time thinking about this at some point,
> because CSS as it is now really frustrates me. The tsuris seems mostly to
> revolve around the fact that CSS is not designed to support the new Web
> applications which want to keep all their content inside the viewport and
> create overflowed scrolled sub-areas instead of overflowing the viewport.
> Am I missing some easy way to do the following example?
> For example, I current have a need to do something like this for my social
> network site:
> <div>some header content, even has a float:right so it fills the width of
> viewport</div>
> <table>
>   <tr>
>      <td><div id='leftPane' style='width:50em; height:?;
> overflow:auto'></div>
>      <td><div id='rightPane' style='width:?; height:?; overflow:auto'>
>                <textarea...><textarea>
>                <div id='ChatText' style='width:30em; height:?;
> overflow:auto'></div>
>             </div>
> </table>
> What I want is for those height:? to fill up the viewport from their
> inline locations to the bottom of the viewport. Ditto the width:? for the
> viewport width. So I never want the viewport to scroll, I just want my
> overflow:auto to absorb all the overflow.

As far as I understand you will need flex units with template layout here.

With flex units and the flow this layout can be defined as

   flow: "1 1"  // header (first child) spans two columns
         "2 3"; // leftPane, rightPane
   height:*; // spans whole viewport

     some header content, even has
     a float:right so it fills the width of viewport</div>
  <div id='leftPane' style='width:50em; height:*;
  <div id='rightPane' style='width:*; height:*; overflow:auto'>
      <div id='ChatText' style='width:30em; height:*; overflow:auto'></div>

'*' above is '1*' - one unit of free space left in container.

div#ChatText will expand to the height of 'rightPane' pane minus
height of the textarea so textarea will be at the very bottom of

Obviously you do not need any artificial DOM elements here.

See: "3.5. flow:"template"" in

To calculate flex units you will not need generic constraint solver.
The algorithm of flex computations is not more complex than for tables.

Or did I miss something in your messages?

> What I am forced to do now is use JavaScript on a viewport load and resize
> events, to calculate those. It is very messy and obfuscates the semantics
> of my layout.
> With the generalized edge based layout proposed in this thread, I could
> easily achieve the above example.

Andrew Fedoniouk

Received on Saturday, 23 October 2010 02:53:27 UTC

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