This is the monthly archive for February 2016.
Instead of the work I was supposed to do I spent about a day and a half on the alpha version of a viewports visualisation app that, oh irony of ironies, only works on desktop browsers because of the necessary space.
It’s already been very useful to me, since figuring out how the viewports actually work is necessary for full understanding. I hope it does the same for you.
It also contains an example of absolute, fixed, and device-fixed position so that you understand the difference.
The app is by no means ready; there’s a ton of features I’d like to add. Still, for now I’ve run out of time, and as long as it’s impossible to actually make money with such apps I’m not sure how much time I’m willing to spend on it.
11 February 2016
Last week I found out that as of Chrome 48
window. no longer exposes the dimensions of the visual viewport. Instead, it now exposes the dimensions of the layout viewport, and is thus a copy of
I’m not happy with this change. So it’s time for me to don my ceremonial robes as Guardian of the Viewports and ask the Chrome team to revert this change and restore the visual viewport to its rightful place.
There are three reasons why I think Chrome is making a mistake here:
The situation is less dire than I assumed. About 90% of the users do in fact use the latest Chromium WebView. This number is based on several hundred million hits in December 2015, primarily from North America and Europe.
See the January 2016 archive.
I’m around at the following conferences: