It looks like Chrome has updated by itself, and as with all improvements to software, more bugs have been introduced.
You can blame our programming skills, but here is how the home page of Lucire now looks (and it had looked like this on Chromium a couple of months ago, too):
Below is how it looks today on Firefox, but it looked roughly like this on old Chrome, as it does on Opera, IE8, and Maxthon, using HTML techniques that we had used since there was HTML:
Here’s another regular Chrome bug, where it just misses text altogether (though the text usually returns on a reload):
The same bit on Firefox:
This is one annoying browser if it can’t even display basic HTML text.
As expected, none of my reported bugs (incomplete font menus, inability for Chrome to switch character sets when encountering different languages on a page) have been ﬁxed—but, then, that’s the Google way.
Meanwhile, Firefox 3·6·12 has returned to its extremely crashworthy ways (four times per day), despite the tech help from two friends. One friend, Andrew, suggests I should call these Flash crashes, rather than Firefox crashes, because it could be Flash at fault. Certainly there are enough times when the plug-in container crashes just prior to the whole browser failing. On the Mozilla forums, there is another user who has a clean install of Firefox with no plug-ins, and he reports constant crashing, too.
Browsing through the about:crashes in my Firefox reveals an error headed by:
in the majority of the last 10 cases. Here’s Mozilla’s page on that error which, if I read correctly, they haven’t a clue how to ﬁx.
I wish I could roll back to the stable 3·6·10, and, as mentioned, 3·0 was one of the most stable releases Mozilla had till it got into the double-digit sub-subversions (it must have been around 3·0·12).
Programs crashed as often 15–20 years ago, but usually that was due to memory or disk space issues. Code just seemed tighter, programmers were able to do more amazing things given the constraints, and the software more efﬁcient. Now they crash on the oddest things and, it seems, every browser is anachronistic in some way. All I ask is for a browser that: (a) does not crash when you blink your eyes; (b) displays the complete font menu; (c) does not change font because you have used quotation marks or a ligature or other characters within the set font’s character set; (d) kerns and allows font-face; (e) changes font when it realizes that the selected one lacks glyphs for a foreign character set; (f) interprets HTML properly.
Right now, here’s how they stack up:
|Internet Explorer 8||*||*||*|
Chrome is by far and away the quickest on the block, but when it messes up on everything else, it’s just not going to cut the mustard. It might crash less often than Firefox but it still crashes, and it does other things poorly. Someone wake me when Chrome comes out of alpha, because that’s where it belongs; or when Mozilla acknowledges the feedback that 375 people (and counting) are having with Firefox constantly dying on us.
If Opera can sort out its font issues, then it has a real chance of being the best browser out of the lot.