- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 18 Sep 2013 10:07:44 -0700
- To: "Robert O'Callahan" <robert@ocallahan.org>
- Cc: www-style <www-style@w3.org>
On Tue, Sep 17, 2013 at 8:11 PM, Robert O'Callahan <robert@ocallahan.org> wrote: > As we all know, overflow:scroll/auto elements re funky because scrollbars > can be inserted between the padding and the border. This means the content > and padding boxes for such an element are smaller than you'd expect based on > 'width', 'height' and 'padding' properties. For example: > <div style="overflow:scroll; width:200px; height:200px; > padding:10px">...</div> > The children of the <div> will flow into an area that's less than 200px - > 10px - 10px wide, if the platform uses scrollbars that need width. > > I'm wondering whether to make getBoxQuads subtract scrollbar widths when > computing the size/position of the 'content' and 'padding' boxes for an > overflow:scroll/auto element. Any thoughts? Yes, the whole point of these new APIs is to expose the correct information in a simple way. Scrollbars shrink the padding box, so asking for the padding box should give you the correct (smaller) value. ~TJ
Received on Wednesday, 18 September 2013 17:08:31 UTC