- From: Ojan Vafai <ojan@chromium.org>
- Date: Thu, 22 Sep 2011 14:51:55 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: www-style@w3.org, David Hyatt <hyatt@apple.com>
Received on Thursday, 22 September 2011 21:52:40 UTC
On Wed, Sep 21, 2011 at 5:15 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote: > On Wed, Sep 21, 2011 at 3:22 PM, Ojan Vafai <ojan@chromium.org> wrote: > > 2. "7.3.1. Auto-sizing in Orthogonal Flows > > If the computed measure of an element establishing an orthogonal flow is > > ‘auto’, then the used measure is calculated as > > the fit-content (shrink-to-fit) size using the initial containing block's > > size as the available measure." > > We should instead use the available size if there is one and only use the > > initial containing block's size if there isn't one. > > <div style="height: 100px"> > > <div style="writing-mode: vertical-lr; height: 100%"></div> > > </div> > > Using the initial containing block's size as the spec currently says to > > would result in the inner div overflowing outside of the outer div. It > seems > > clear to me that any developer would expect the inner div to be 100px > tall. > > Agreed. My original email wasn't 100% clear. I think the available size should be use for percentage sizes as well as the size to use for the shrink-to-fit algorithm for auto-sizing.
Received on Thursday, 22 September 2011 21:52:40 UTC