- From: James Robinson <jamesr@google.com>
- Date: Tue, 4 Dec 2012 09:26:01 -0800
- To: Sylvain Galineau <sylvaing@microsoft.com>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, "www-style@w3.org" <www-style@w3.org>
Received on Tuesday, 4 December 2012 17:26:28 UTC
On Tue, Dec 4, 2012 at 9:01 AM, Sylvain Galineau <sylvaing@microsoft.com>wrote: > > [Boris Zbarsky:] > > > > On 12/3/12 6:02 PM, Tab Atkins Jr. wrote: > > > In the two browsers that currently support vw/vh, Chrome and IE, > > > neither one pays any attention to scrollbars. > > > > Neither does Gecko (which has vh/vw on the Aurora channel at this point), > > fwiw. > > > Wouldn't such a requirement also make implicit assumptions about > scrollbars' > UI model? On many touch devices scrollbars are overlaid on top of the > content > only when the user is touching/panning the screen. Recalculating viewport > units > and reflowing when that happens would clearly be horrible; preventing the > app > from using that part of the viewport would also be sub-optimal, if only > because > these scrollbar designs were at least partly motivated by the desire to > avoid > wasting precious screen real estate. I wouldn't expect such > implementations to > bother fixing the testcase fails they would get from this requirement. > > Overlay style scrollbars do not change the layout width/height of the page and so should be excluded from vw/vh, IMO. - James
Received on Tuesday, 4 December 2012 17:26:28 UTC