Comments on: The Moz Cause http://blog.markparuzel.com/2008/03/09/the-moz-cause/ Segmentation Fault Fri, 12 Mar 2010 06:21:57 +0000 http://wordpress.org/?v=2.2.1 By: Mark http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2811 Mark Mon, 24 Mar 2008 13:10:22 +0000 http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2811 Good comments. I might have been a bit over zealous with my post. Thanks everyone. Good comments. I might have been a bit over zealous with my post. Thanks everyone.

]]> By: MacRenegade http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2810 MacRenegade Mon, 24 Mar 2008 13:06:52 +0000 http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2810 Actually Safari 3.1 (with the normal webkit build) got 74%. Actually Safari 3.1 (with the normal webkit build) got 74%.

]]> By: Nemo http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2698 Nemo Mon, 17 Mar 2008 12:36:22 +0000 http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2698 Javascript and CSS code may seem arcane to the average browser user. But when they visit a web site, they expect the page to be rendered in a manner that allows them to access the content as the developer of the page intended. We've been browsing for decades through pages whose markup includes specific work-around-code to handle specific browsers which don't render correctly, render in peculiar manners, or worse, don't render at all. On the web developer side, and the user, attaining a greater level of compliance to a web standard for rendering content only helps make everyone's browsing experience better. W3C's Acid test will likely end up being one of many developed for this purpose, and kudos to them for coming up with the idea. It's working, developers are paying attention, and doing their best to make their browsers compatible... Well, most are ;) Javascript and CSS code may seem arcane to the average browser user. But when they visit a web site, they expect the page to be rendered in a manner that allows them to access the content as the developer of the page intended. We’ve been browsing for decades through pages whose markup includes specific work-around-code to handle specific browsers which don’t render correctly, render in peculiar manners, or worse, don’t render at all.

On the web developer side, and the user, attaining a greater level of compliance to a web standard for rendering content only helps make everyone’s browsing experience better. W3C’s Acid test will likely end up being one of many developed for this purpose, and kudos to them for coming up with the idea. It’s working, developers are paying attention, and doing their best to make their browsers compatible… Well, most are ;)

]]> By: n/a http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2564 n/a Mon, 10 Mar 2008 09:42:52 +0000 http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2564 Both of them are developing to pass ACID3, Firefox stepped up 10% from its last beta release (beta4pre to beta5pre) and coming up! Both of them are developing to pass ACID3, Firefox stepped up 10% from its last beta release (beta4pre to beta5pre) and coming up!

]]> By: Andre Guibert de Bruet http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2560 Andre Guibert de Bruet Mon, 10 Mar 2008 06:45:22 +0000 http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2560 Though I am not much of a Safari fan myself, I will say that my browser of choice, Firefox, isn't exactly standards-compliant. There are literally tens of thousands of feature nuances to check for, and browser developers have to spend a considerable amount of time chasing the ones that are used in benchmarks to "make the grade". There were a couple of interviews of the Safari developers that were posted online about 18 months ago, that stated that Apple is striving for 100% Acid compliance (Acid 2 was the suite they were trying to comply to at the time). Based on the fact that Mozilla is largely developed by volunteers that do not spend most of their working hours working on Gecko, I am impressed by how well it has fared compared to the other browsers in the list. My own testing has Internet Explorer 7 (7.0.6000.16609) running on Vista Ultimate x64 chiming in at 5/100 (Five out of one hundred). Once again, there is more to a browser than strict Acid compliance. Things like look and feel, responsiveness and ease-of-configuration matter a whole lot to the average user than passing arcane Javascript and CSS-based tests. Though I am not much of a Safari fan myself, I will say that my browser of choice, Firefox, isn’t exactly standards-compliant. There are literally tens of thousands of feature nuances to check for, and browser developers have to spend a considerable amount of time chasing the ones that are used in benchmarks to “make the grade”. There were a couple of interviews of the Safari developers that were posted online about 18 months ago, that stated that Apple is striving for 100% Acid compliance (Acid 2 was the suite they were trying to comply to at the time). Based on the fact that Mozilla is largely developed by volunteers that do not spend most of their working hours working on Gecko, I am impressed by how well it has fared compared to the other browsers in the list. My own testing has Internet Explorer 7 (7.0.6000.16609) running on Vista Ultimate x64 chiming in at 5/100 (Five out of one hundred).

Once again, there is more to a browser than strict Acid compliance. Things like look and feel, responsiveness and ease-of-configuration matter a whole lot to the average user than passing arcane Javascript and CSS-based tests.

]]> By: Mazhar http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2557 Mazhar Mon, 10 Mar 2008 04:56:16 +0000 http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2557 Well theres a reason given on the safari blog (http://webkit.org/blog/158/the-acid-3-test/) Well theres a reason given on the safari blog (http://webkit.org/blog/158/the-acid-3-test/)

]]> By: Kriss http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2555 Kriss Mon, 10 Mar 2008 04:53:09 +0000 http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2555 Actually, if you look a bit closer, it'll tell you some more. Firefox release beats Safari 3 release, while Safari nightlies beat Firefox nightlies. All in all, the Safari chaps seem to be fixing the issues (at a good rate at that) - the Firefox maintainers do it as well, obviously, looking at progress of nightlies vs. release/beta/whatnot. Actually, if you look a bit closer, it’ll tell you some more. Firefox release beats Safari 3 release, while Safari nightlies beat Firefox nightlies. All in all, the Safari chaps seem to be fixing the issues (at a good rate at that) - the Firefox maintainers do it as well, obviously, looking at progress of nightlies vs. release/beta/whatnot.

]]> By: Anonymous Coward http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2552 Anonymous Coward Mon, 10 Mar 2008 04:14:41 +0000 http://blog.markparuzel.com/2008/03/09/the-moz-cause/#comment-2552 The version of Safari that scored 90% was the nightly build (as was the top version of Firefox). Safari 3 scored 39% and was indeed handily outscored by Firefox 2 (52%). Also, the Acid Tests aren't really standards -- the W3C standards are the standards. The acid tests are just... well, tests. They stress test the browser in odd and difficult rendering jobs, and give developers an idea of where the problems in their render engine are. Like any test, though, it can be a bit artificial, and it doesn't test everything; instead it tries to test the subset of the cases that people care the most about. Developers could certainly push up their Acid3 scores at the cost of putting energy elsewhere, if they so desired, so as you indicate, it's really just a guideline. But it's the best we've got. The version of Safari that scored 90% was the nightly build (as was the top version of Firefox). Safari 3 scored 39% and was indeed handily outscored by Firefox 2 (52%).

Also, the Acid Tests aren’t really standards — the W3C standards are the standards. The acid tests are just… well, tests. They stress test the browser in odd and difficult rendering jobs, and give developers an idea of where the problems in their render engine are. Like any test, though, it can be a bit artificial, and it doesn’t test everything; instead it tries to test the subset of the cases that people care the most about. Developers could certainly push up their Acid3 scores at the cost of putting energy elsewhere, if they so desired, so as you indicate, it’s really just a guideline. But it’s the best we’ve got.

]]>