Below you find the last seven QuirksBlog entries.
After last week’s rant about, among other things, the W3C Device Adaptation spec, one of the spec’s authors asked me to clarify my critique. Fair enough. Here’s my take on the current specification.
My critique of Device Adaptation consists of three main themes:
- The spec does not address the actual current situation at all, while all browsers actually support my theory of the layout, visual, and ideal viewports decently, and I’ve already done the heavy lifting.
- The spec is obscure about what its most important components actually mean; I’m especially thinking of the initial and actual viewport. A simple schematic would have helped a lot here, and it’s fairly easy to produce.
- Although the spec treats relevant media queries as well as the meta viewport and the
devicePixelRatio. That latter, especially, could do with some specification.
Today I rant about undocumented Chrome features and unreadable W3C specs. There’s too much of both nowadays, and I’m getting VERY tired of both. Google and W3C should clean up their act.
During my research of modern input types such as
number I stumbled upon the
type === 'text' detection, mostly in order to cater to Android WebKit, although it also solves a few other problems.
Yesterday, in reaction to pointer events becoming a W3C recommendation, Tim Kadlec published an important piece about Apple’s huge influence on the mobile web.
I agree with him to the extent of writing this extended Me-Too entry. It is increasingly becoming necessary to do something about Apple, its absolute refusal to talk to anyone, and its dickish way of bending the mobile web to its desires. Personally, I became tired of Safari quite a while ago, and I wouldn’t mind taking Apple down a notch.
So let’s do it.
Mobilism, 27th of March in Amsterdam, is going to be a stellar conference. All the content is in, and we're excited. What about you? Judge for yourself.
Last week Niels Leenheer of HTML5 Test told me he’d released a simple Android app that mimics a browser but runs in the device’s WebView. This is ideal for testing WebViews, a topic I’ve ignored so far.
I downloaded the app to all my Android 4/5 phones except for the Huawei C8813 (Chinese firmware) where Google Play won’t run, and the LG L5, where the app crashes when you try to load a page, and catalogued which browser the WebView is (or purports to be). Here are the results:
From last Thursday to earlier today I held a simple one-question poll about which advanced input types such as
number web developers are using.
The results are surprising, while I expected
number to end in first and second place, the most popular type was actually
Even older entries
See the February 2015 archive and beyond.