- From: Anne van Kesteren <annevk@opera.com>
- Date: Tue, 25 Dec 2007 13:16:47 +0100
- To: "Alex Mogilevsky" <alexmog@exchange.microsoft.com>, "robert@ocallahan.org" <robert@ocallahan.org>
- Cc: "www-style@w3.org" <www-style@w3.org>, "Sam Fortiner" <samfort@microsoft.com>, "Harel Williams" <harelw@microsoft.com>, "Scott Dickens" <sdickens@exchange.microsoft.com>
On Sun, 23 Dec 2007 22:09:57 +0100, Alex Mogilevsky <alexmog@exchange.microsoft.com> wrote: > I agree since there is nearly perfect interoperability, behavior should > not change. I would prefer the spec to be more clear here though > (current state is somewhere between ambiguous and incorrect). That would be good, indeed. However, it should probably be still be phrased in a way that the user agent only needs to follow these rules if you are using scrollbars for this purpose and not when using another mechanism to scroll. > How about this: > > "The space taken up by the scrollbars affects the computation of the > dimensions in the rendering model.<INS>Exact effect of scrollbar on > formulas in sections 10.3 an 10.6 are UA-specific but UA must ensure > that adding or removing scrollbar never changes dimensions of border box > of an element. In other words, changes to ‘overflow’ property may affect > layout within the element but not layout of any content around it.</INS>" > > Ideally, it would tell what exactly happens to ‘width’ and ‘height’ when > a scrollbar is added. I think there is enough interop so that formulas > can be defined precisely, but that certainly is a bigger change. > > As far as affect of scrollbar on available size for content, the interop > is far from perfect, that would be something to clarify in CSS3. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Tuesday, 25 December 2007 12:14:54 UTC