Everyone kept going on about how fast Chrome after it came out. My experience has been the opposite. A few months back every time I would start Chrome it would sit for half a minute, discovering proxy, I think. It hasn’t really altered my browsing experience once it got started. That was fixed a while back.

Now I have found more issues that actually make it the slower browser out of IE(!!!) and Firefox. Try browsing this site:

24ways.org

Yeah. You can’t scroll for shit.

Fair enough, it’s a bug. That’s OK, we all write bugs. I would have completely not cared if not for yet another Chrome idiosynchrasy that just tipped me over the edge.

The layout that I am working on is largely inspired by 24ways.org, so it has a few semi-transparent elements, which of course don’t work in IE. As a workaround I am using one pixel PNGs with alpha channel. Supposedly this is the way to do it:

.transparent {
  background: url(pngwithalpha.png);
  background: rgba(255,255,255,0.1);
}

What the browser is meant to do is to disregard the first background declaration and use the second if it supports RGBA colours. That’s what Firefox does… But no, Chrome loads those images anyway.

Fair enough, it has quirks. At least it would cache the images, right? WRONG!!!. Unlike Firefox and IE, Chrome would request those image even though you don’t refresh the page. Both IE and Firefox, when you focus on the address bar and hit enter will retrieve the images from local cache. When you refresh, they would do an If-Modified-Since request. Chrome does an If-Modified-Since request regardless.

Actually, I lie. It doesn’t do the request regardless. It will do a status request for images that are visible straight away. If there is a background image that is in a :hover pseudo-class, it will retrieve that one from the local cache. Go figure.

Here is an excellent and very detailed comparison of browser support for transparencies and pngs. Go Firefox!!!