Posted in Technicalon Sep 8, 2008
In March I ran the Acid 3 web browser stress test against all the most modern browsers at the time to see how they performed. Since then, there are new versions of browsers which justify a re-run of the tests. Here are the results:
All the web browsers were run on the same Windows XP system.
Then, out of curiosity, I decided to check the memory usage of each browser and found the following:
Posted in Technicalon Mar 5, 2008
The Acid tests are various tests for web browsers to see how well they can adhere to standards. If a web browser was a computer science project, these would the tests the teaching assistant would run on your project to see how well you did and to assign you a score.
The Acid3 test was recently released, and I ran it on a few web browsers I had installed here. Here is how they performed:
I also ran it against Konquerer on Linux, but it kept crashing. Other people are reporting other various scores with various versions.
Update March 7. I’m a little confused about how the tests work. For example, I’ve run it multiple times on the Flock browser, but I’ve seen three different scores come out. I’m confused how the same test can yield different results at different browsers on the same browser. I want things to be more deterministic.
Update March 25. I ran the tests against the new Safari 3.1 on windows, and it scored an impressive 75/100.
Update March 26. Firefox 2.0.0.13 on Windows scored for me today a 53/100.
Posted in Technicalon Dec 9, 2007
Today I discovered that a link to a post on my blog is included in the source to JBoss Richfaces. The blog post that was referenced was a small note I made about bug in the Safari web browser. They provided a workaround in Javascript code for a suggestion box, and they referenced my post in a comment in the source code.
It makes me feel good when I see things that I’ve written appear in real-world applications. It is also nice that the source code is open, which means that anyone can look at it and appreciate my website address.
Posted in Technicalon Feb 20, 2006
I found what seems to be a bug in the Safari web browser recently. The problem occurs when there is a table, and you are trying to find the offsetTop property of a row in that table. I have an example that illustrated the problem when in Safari.
Recent Comments