QuirksBlog monthlies

This is the monthly archive for January 2014.

Touch action tests

Permalink | in Content, Touch events

Just now I published the latest touch action tests. There are no nasty surprises, although IE remains idiosyncratic.

The most common touch action is the single tap. When that action occurs, browsers fire off a whole slew of events, mostly in order to remain backward compatible with older sites that only use mouse events. Although there are quite a few deviations from the “standard” order of these events, they don’t matter much. The average script won’t break because the mouseover event fires before the touchstart event. Still, I documented all deviations. Who knows when this will come in handy?

I also studied the double tap, pinch-zoom, and scroll actions and found that browsers generally fire those events you would expect. The contextmenu event, which could serve as a useful proxy for a touchhold actions, is badly supported.

I also updated the mobile events page with the new information gleaned from these tests.


CSS Day 2014

Permalink | in CSS Day

We proudly announce CSS Day 2014, 4th of June, in Amsterdam, eight top speakers, eight CSS dev topics.

Early bird has started. Grab those tickets now for € 200 instead of € 275. And there’s only 50 of them.

Who are the speakers, you ask? Sorry, we won't tell you. We'll reveal them on 4th of February, but early bird ends at that precise moment in time. Do you trust us? Then order now!

Also, summer in Amsterdam.

Browser stats for Q4

Permalink | in Market share

It’s time for some browser stats, as always courtesy of StatCounter.

StatCounter has rolled out a major upgrade to its statistics. For the first time, tablets are now clearly separated from desktop. If you haven’t taken a look for a while, do so now.

continue reading

width=device-width, initial-scale, and too-wide elements

Permalink | in Viewports
0 comments (closed)

Just some random notes from the trenches in order to show everyone that, despite appearances, the viewport is not simple or easy to understand.

A browser vendor asked me to study the following problem:

  1. A page has width=device-width, or initial-scale=1, or both.
  2. The page also has an element of 1600px wide; far too wide for the layout viewport that’s normally created by the meta viewport.
  3. Should the browser zoom out in order to show the entire 1600px-wide element? Or should it ignore the wide element and show the usual result of 320-400px?

continue reading


See the December 2013 archive.

This is the blog of Peter-Paul Koch, web developer, consultant, and trainer. You can also follow him on Twitter or Mastodon.
Atom RSS

If you like this blog, why not donate a little bit of money to help me pay my bills?