Below you find the last seven QuirksBlog entries.
Last week I found out that as of Chrome 48
window.innerWidth/Height 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:
- It breaks the web. ALL other browsers support this.
- It takes one simple trick for web developers to avoid problems with these properties, so the change is not necessary.
- It chokes innovation, in particular zoom-based layouts.
After my recent post about updating Chromium WebViews I was contacted by Scientia Mobile, the company behind the WURFL database, and was offered actual real-life stats!
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.
This week I received my first gift phone in ages, and since the sender wants me to test it I had to go through all my dozen Android phones and update them as well, so that I can run tests against the latest installed Chromia.
During this process I began to have serious doubts about the update process of the Chromium WebView especially, though the same problems also crop up with regular Google Chrome.
TL;DR: Although, as promised, the Chromium WebView can be updated as a stand-alone app from Android 5 on, I doubt if consumers actually do so because Android’s update process is badly broken. Thus a wide variety of WebViews may be in use right now.
Fair warning: if you are unable to contemplate the simultaneous existence of several Chromium versions running on the same device without suffering from existential angst the reading of this article is discouraged until you’ve consulted your psychiatrist.
Last week, after reading this article, I tweeted that Firefox OS is dead. There was some pushback, since despite some important updates the OS will continue to be developed. However, an OS can be functionally dead without development being ceased, and that’s what I meant in my tweet.
I made a mistake in yesterday’s article. Not a technical mistake, but an MDN-reading mistake. The reasons why I did so are moderately interesting for MDN users, and suggest a few improvements for the site.
A quick note on styling placeholder texts. Although it’s very easy, it turns out that both MDN and the usual go-to CSS Tricks article leave out one important bit of data: when setting the
color you should add
opacity: 1 for Firefox.
I’m currently working on my first real paid coding project in ages: PvdApp, a project of a friend of mine. (He paid for this research, so he deserves a link.)
Among other things, this project requires me to style and script sliders. There are several interesting points I would like to bring to your attention, such as a few underreported IE problems, the solution to Android WebKit’s appearance bug, and the proper use of the input and change events. And a quick syntax overview is always useful.
Even older entries
See the November 2015 archive and beyond.