Below you find the last seven QuirksBlog entries.
Everyone who’s ever messed around with dates knows that they are terribly user-hostile — not only for software developers, but also for users. True, users will be able to tell you their date of birth or today’s date without trouble, but ask them to fill them out in a web form and they will encounter problems.
Month first, day first, or year first? And what about slashes, dashes, and other separators? Usually the website engineer has a strong personal preference and enforces it religiously upon unsuspecting users with stern and incomprehensible error messages in a lurid shade of red that are too tiny for anyone over 25 to read.
(This article was originally published on Samsung Internet’s Medium channel. Since I do not believe Medium will survive in the long run I re-publish it here.)
Last week I was the target of a good old-fashioned internet witch hunt when I dared to propose that you should be able to work without tools (frameworks, libraries, and so on) in order to be a web developer.
It’s that time of year again; today we announced most of the line-up for our fifth annual CSS Day conference in Amsterdam — and we think it’s a wonderful one, though naturally we’re biased.
Once more Scientia Mobile sent me their Android WebView stats over the third quarter. I edited them slightly and put them online.
Three weeks ago I redid my mobile viewports tests for the umpteenth time, and today I give you my overview. There is some progress to report, but also a lot of changes.
screen.width/height now gives the dimensions of the ideal layout viewport in nearly all mobile browsers.
getBoundingClientRect() is relative to the visual viewport in most browsers, but relative to the layout viewport in Chromium 50+ and Edge.
Touch/Click.clientX/Y has the same problem: it is relative to the visual viewport in most browsers, but relative to the layout viewport in Chromium 45+ and Edge.
Touch/Click.screenX/Y is still chaotic. Don’t use.
- The Chromium WebView does not obey the meta viewport.
- I found a difference between Android WebKit the browser and Android WebKit the WebView. This is the first such difference I know of.
- I found a way of calculating the combined height of the browser and system toolbars in most browsers in some situations.
- We need more properties. A list can be found below.
Just now Smashing Magazine published Introducing Samsung Internet, an article I wrote about Samsung’s Chromium 44-based default browser with the fairly unimaginative name. It also contains an interview with Samsung Internet engineer and W3C luminary Jungkee Song about the browser and the ideas behind it.
Sometimes I read a paragraph that makes me wish I had written it. Last Monday that happened again: I became profoundly jealous when I read this:
We know libraries, in fact, we have the best libraries. Our libraries are huuuge
It’s the best part of a hilarious dialogue (that I also wish I’d written) between a newbie web developer who needs a simple REST/Ajax site and an “experienced” front-end engineer who patiently explains the insane amount of tooling this requires nowadays. Read it for yourself. It’s worth it. I’ll wait.
The dialogue pokes fun at what passes for modern web development; especially our infatuation with tools, and it succeeds admirably. The purpose of my post is not to react to the article itself, but to two other reactions I read.
Even older entries
See the October 2016 archive and beyond.