Viewport height is taller than the visible part of the document in some mobile browsers
When trying to use a
100vh CSS value to build a new interface for a game that would use the full viewport, I discovered that this full height value meant the bottom of the game interface was partialy hidden behind the browser buttons bar or below the "fold" of some mobile browsers.
I first discovered this on my iPhone 5 and iPad 2.
Here is what this page looks like on an iPhone 5 :
100vh is computed for when the browser interface is hidden, after a scroll :
When trying to use a
100vh CSS value to build an interface for a game that would use the full viewport, I discovered that this full height value meant the bottom of the game interface was partialy hidden behind the browser buttons bar of Safari iOS on iPhone, or below the "fold" on iPad.
- Open http://lab.gasteroprod.com/vub/index-ios-issue.html on iOS Safari with an iPhone in portrait mode, or an iPad in portrait or landscape mode
- The bottom part of the "bottom right" box is not visible, the 100vh height container being taller than the visible part
I would have expected the viewport size (and the
100vh dimension) to be equal to the visible part of the page in the browser. It's called VIEWport after all.
I understand it means the viewport changes when the browser interface hides, but I find it better, and necessary for "full viewport" interfaces. Fullscreen API is not available either, so there is no simple way to fix this behavior.
The bottom part of the "bottom right" box is not visible, the
100vh height container being taller than the visible part
iPhone 5 and iPad 2
iOS 8.1.3 (12B466), and other versions in the iOS simulator
In fact I saw later that iOS Safari is not the only one doing this.
I discovered later the same behavior on the browser of Firefox OS:
Are these behaviors browsers bugs, or the correct implementation of the standard, or is it open to interpretation?
Webkit bug has been set to RESOLVED WONTFIX, with this explanation:
This is completely intentional. It took quite a bit of work on our part to achieve this effect. :)
The base problem is this: the visible area changes dynamically as you scroll. If we update the CSS viewport height accordingly, we need to update the layout during the scroll. Not only that looks like shit, but doing that at 60 FPS is practically impossible in most pages (60 FPS is the baseline framerate on iOS).
It is hard to show you the "looks like shit" part, but imagine as you scroll, the contents moves and what you want on screen is continuously shifting.
Dynamically updating the height was not working, we had a few choices: drop viewport units on iOS, match the document size like before iOS 8, use the small view size, use the large view size.
From the data we had, using the larger view size was the best compromise. Most website using viewport units were looking great most of the time.
The issue on Apple Bug Reporter has been closed with this comment:
This issue behaves as intended.
The W3C CSS Working Group replied on Twitter with links to past discussions:
The W3C CSS Working Group suggestion doesn't fix anything, in iOS at least. Test it live here.
Boris, a friend, told be he saw a disturbing behavior of my text content when scrolling on this site:
@nhoizey j'ai un changement de taille de police au scroll… Bizarre!
— Boris 🚀 (@borisschapira) June 30, 2015
In fact, the viewport height changes when he scrolls and the browser chrome hides. Combine this with the fact that he
font-size is partialy based on a
vh value, and you understand that when scrolling and hiding the browser chrome, the text size was growing.
Boris uses a OnePlus One running Android 5.0.2 and Chrome 43.0.2357.93.
So there is at least one browser that behaves as I want for my full height game screen… but it makes users wonder if there is an issue…
People developing Chrome for Android now plan to change its behavior to match iOS Safari's one, claiming that “Safari’s been doing this for years without user/developer complaint”.
Chrome will indeed now work like Safari.
There is a lot of interesting informations in this study about the differences between mobile browsers, and the proposed consensus.
David Bokan explains how Chrome will now behave starting with version 56: URL Bar Resizing.
The unintuitive choice of making vh units the largest possible viewport but the ICB the smallest possible is to match Safari's behavior.
Jeremy Keith made the same observation, and concluded that "the result of this messiness is that the vh unit is practically useless for real-world situations with real-world devices".
Peter-Paul Koch makes the same observation that viewport size is a tricky topic, with many disparities among browsers, in his post Toolbars, keyboards, and the viewports.
If you want to share an error or suggest an enhancement of this content, please edit the source on Github.