QuirksBlog - Chrome

.
Part of Browsers.

Suppressing the 300ms click delay

Permalink | in Chrome, Touch events

By default, if you tap on a touchscreen it takes about 300ms before a click event fires. It’s possible to remove this delay, but it’s complicated. I investigated it.

continue reading

Blinkbait

Permalink | in Chrome, Opera Mobile/Mini

A few more Blink-related links. (This article’s title was stolen borrowed from Thomas van Zuijlen.)

continue reading

Blink

Permalink | in Chrome

So Google created Blink, the new rendering engine for Chrome and Opera. What exactly is going on, and what will the consequences be?

continue reading

WebKit on Mobile, take 2

Permalink | in Apple, Chrome, Google, Safari, Samsung
12 comments (closed)

When I reviewed the reactions to my There is no WebKit on Mobile post, it became pretty clear that few had expected its conclusion that there is no single WebKit on Mobile. Overall, it seemed that most people were pretty surprised, and hurried to revise their ideas of the mobile browser market. That was the point of the article, so I was happy.

The most-often heard criticism was that I was unclear about the browser version numbers. That’s true, and I have updated the table to include them. I also split out the tests into Acid, CSS2, CSS3, HTML5, and JavaScript, and calculated separate scores for each browser. The results are interesting for some browsers. Konqueror sucks at JS but is very good in CSS, while Android is exactly the opposite. Interesting data.

(I’m still tinkering with the interface, by the way, and I didn’t have the time to finish my current revision. So the coloured bars are temporarily gone, but they’ll return in the future.)

continue reading

There is no WebKit on Mobile

Permalink | in Apple, Chrome, Google, Mobile, Safari, Samsung
32 comments (closed)

Last week I spent a lot of time on WebKit in order to produce a comprehensive comparison of all WebKits. My purpose was to prove there is no “WebKit on Mobile,” and to gain some more insight in the complicated relations between the various WebKits.

Therefore I now present the Great WebKit Comparison Table. In it I compare 19 different WebKits on 27 tests.

continue reading

Google Chrome Frame — technical notes

Permalink | in Chrome, IE
10 comments (closed)

Well, Google Chrome Frame has certainly taken the web dev world by storm. It’s almost as if people are fed up with Internet Explorer and welcome an alternative.

Many useful things have already been said about Frame. I’d like to add a few technical notes I haven’t yet encountered anywhere else.

continue reading

State of the Browsers

Permalink | in Browser Wars, Chrome, Content, IE, Safari
35 comments (closed)

There’s some browser news to discuss, and I thought I’d bundle it all in one entry. Maybe I’ll even do this more often; it seems a good feature for this blog. But I’m not promising anything!

This weekend I started testing some new browsers, and meanwhile I’ve updated the HTML and CSS tables. There were no surprises. I’m continuing with the Events tables, but they’re so large and sometimes so complicated that I’m not sure when I’ll finish.

In this installment we’ll take a look at IE8RC1 and some reactions to it, Safari 3.2, Chrome’s lack of a “Check for updates automatically” feature and Opera’s antitrust complaint.

continue reading

Four browser notes

Permalink | in Chrome, IE, Opera
19 comments (closed)

In case you’re wondering why this blog is updated so rarely; I’m taking a slight break from web development, and I’m working on a major upgrade of my Dutch politics section. It’s not ready yet; I’ll let you know when it is.

However, while working on it I found a few browser peculiarities, and I thought I'd let you know. There’s one IE bug; one case in which IE does the right thing and the other browsers don’t; the third is a Chrome peculiarity (not a bug); the fourth is an undocumented property in Opera.

continue reading

Google Chrome

Permalink | in Chrome
23 comments (closed)

Just downloaded Google Chrome and did some very brief tests. Rendering engine seems equal to Safari 3.1, as expected. There will be a few minor differences somewhere; I’ll let you know when I find them.

Feels light, quick.

It features a quite slick-looking Firebug clone that includes a YSlow clone. Right-click and select "Inspect element" to access it. Haven’t tried to actually debug with it yet, but it looks promising.

The important points in the Google Chrome story, however, are not about DOM and CSS compatibility, and not even about debugging tools.

John Resig and Alex Russell discuss some ways in which this release could be the start of a new browser war. (Contrary to what Opera states, it hasn’t quite started yet.) I also have a few points to make, but that’ll have to wait for another time.

In order to find out which effect on the market it has, Chrome’s share will have to be measured. Updated browser detect. Detect it by searching for Chrome in navigator.userAgent.
Note to Google Chrome team: please make navigator.vendor read "Google" instead of "Apple".

Which version number does it have? I can’t put a browser without a version number in my Tables. navigator.userAgent says 0.2

Come to think of it, I haven’t yet found any way of disguising it as another browser to get around browser detects written by clueless web developers.

Come to think of it, I haven’t yet found a Preferences menu.

0.2 sounds about right.

But it’s definitely a promising start.

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?

Categories: