- From: David Hyatt <hyatt@apple.com>
- Date: Wed, 08 Feb 2012 10:04:09 -0800
- To: Brad Kemper <brad.kemper@gmail.com>
- Cc: Alex Mogilevsky <alexmog@microsoft.com>, Vincent Hardy <vhardy@adobe.com>, Anton Prowse <prowse@moonhenge.net>, "www-style@w3.org" <www-style@w3.org>
On Feb 8, 2012, at 8:52 AM, Brad Kemper wrote: > On Feb 8, 2012, at 1:28 AM, Alex Mogilevsky <alexmog@microsoft.com> wrote: > >>> From: Brad Kemper [mailto:brad.kemper@gmail.com] >>> Sent: Tuesday, February 07, 2012 6:34 PM >>> >>> What it the purpose of this restriction? If authors wants that behavior, they can >>> just set 'position:relative' on the first block. Why must it be prescribed as a >>> containing block? >> >> Set position:relative on first region or root element of named flow? > > I'm confused by the question, because "root element of named flow" is meaningless to me (or, has been meaningless, or should be meaningless). The root of any HTML document I'd the HTML element viewport, and there is only one root per document. > > I had meant that the author could set position:relative on first region, instead of the first region being the ICB. It seems like that would amount to the same effect, except that it wouldn't be mandatory (the author could leave the first region as static, and the HTML element would remain the true root. I kind of covered this in another message, but I don't think regions themselves should be containing blocks for flow thread content. Rather the ICB for a flow thread should simply match the dimensions of the first region. This is analogous to how the ICB for the root element matches the dimensions of the viewport (or the first page when printing). The ICB for flow thread contents should not be the region itself though. I don't think that makes any sense at all. dave
Received on Wednesday, 8 February 2012 18:08:34 UTC