Slashdot Mirror


IE 5.5 Beats IE6 and IE7 On Acid 3

Steven Noonan sends us to a page where he is collecting and updating results for various browsers on the newly released Acid 3 test. No browser yet scores 100 on this test. (We discussed Acid 3 when it came out.) He writes, "It's not surprising that Internet Explorer is losing to every other modern browser, but how did IE 5.5 beat IE 6.0 and 7.0?" All of the IE versions score below 20 on Acid 3.

58 of 308 comments (clear)

  1. Read that too fast... by palegray.net · · Score: 5, Funny

    IE6 and IE7 On Acid IE's recreational drug use would explain a lot...
    1. Re:Read that too fast... by Mr_eX9 · · Score: 3, Funny

      Sure, invoke Godwin's Law in the third comment, you insensitive clod!

    2. Re:Read that too fast... by Naughty+Bob · · Score: 2, Interesting

      A hand-coded version of Firefox hacked specifically to render Acid 3.
      Why don't we all just use that then?
      --
      "Be light, stinging, insolent and melancholy"
  2. Very simple by Jafafa+Hots · · Score: 2, Insightful
    Microsoft doesn't WANT IE to be compatible. Have the most popular browser and have it not be compatible, and you force everyone to be compatible with YOU - and the competitors who are "standards" compatible are thereby not compatible with what most people was used to, etc.

    If you can't own the internet, this is the next best thing.

    --
    This space available.
    1. Re:Very simple by dedazo · · Score: 2, Insightful

      And they are bringing IE8 into compliance because...?

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    2. Re:Very simple by Bogtha · · Score: 5, Insightful

      Microsoft doesn't WANT IE to be compatible.

      This might fit in well with Slashdot groupthink, but it doesn't fit in well with reality.

      Back when Internet Explorer 6 was being developed, they were in direct competition with Netscape. Internet Explorer 6, when it was released was probably the best browser around when it came to supporting CSS. And you want us to believe that the explanation for 6 being worse than 5.5 in this test was deliberate sabotage by Microsoft?

      They abandoned Internet Explorer development when they won the browser war. Sure, at that point you can make a case for them not wanting to be compatible. But at that point, they weren't developing Internet Explorer at all, so you can't use it as an explanation for Internet Explorer getting worse. And when Internet Explorer development was restarted, they were responding to a call for improved standards support,which they have delivered on.

      I'm sorry, but deliberate sabotage is a ridiculous way of explaining this. Remember, the Acid tests are designed to trigger flaws in popular browsers. Of course it's going to target Internet Explorer 6 and 7 bugs over ancient versions. Internet Explorer 5.5 is no longer popular, so what's the point in ferreting out bugs for the Acid3 test? The real surprise is that people didn't expect this result.

      --
      Bogtha Bogtha Bogtha
    3. Re:Very simple by VGPowerlord · · Score: 2, Interesting

      When did the war actually end? I thought IE5 was the final nail in Netscape's coffin, which would make IE5.5 also after the war ended.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    4. Re:Very simple by Bogtha · · Score: 4, Insightful

      I guess it depends on when you consider the war to have ended, but the important point is that Internet Explorer 6 was indeed a marked improvement in standards support over Internet Explorer 5.5, so it's silly to say that it deliberately does worse in a test written the best part of a decade later. If Microsoft were trying to do worse with Internet Explorer 6, then they failed.

      --
      Bogtha Bogtha Bogtha
    5. Re:Very simple by arotenbe · · Score: 5, Insightful

      Hell, call me when they accomplish anything that plays well with others. In case you haven't been paying attention, IE8 already pass Acid2, which is a strict enough test by itself. Don't tell me that isn't trying to be compliant, especially given IE7's miserable performance at that same test. That and the fact that, unlike any previous release of IE, Microsoft's stated goal for IE8 is to improve standards compliance.
      --
      Tomato wedge sperm darts that are Republican.
    6. Re:Very simple by Spy+der+Mann · · Score: 5, Interesting

      And they are bringing IE8 into compliance because...?


      because they lost the bet. Microsoft expected the force of millions of dollars in propaganda to succeed against those annoying amateurs. But guess what, the amateurs are winning. The book of Mozilla explains it much more elegantly.

      Mammon slept. And the beast reborn spread over the earth and its numbers grew legion. And they proclaimed the times and sacrificed crops unto the fire, with the cunning of foxes. And they built a new world in their own image as promised by the sacred words, and spoke of the beast with their children. Mammon awoke, and lo! it was naught but a follower.
      from The Book of Mozilla, 11:9
      (10th Edition)
    7. Re:Very simple by zippthorne · · Score: 2, Funny

      Look, we were all rooting for Lynx. And they had a good run. But in the end, people wanted a little more. Wishful thinking isn't going to change that.

      --
      Can you be Even More Awesome?!
    8. Re:Very simple by bunratty · · Score: 2, Interesting

      I was also using Mozilla all during 2001, when it was common on Slashdot for people so say that Mozilla 1.0 would never be released. I never thought that it was "doomed to failure". I saw it as the alternative browser with the most potential, even though Opera was more popular then. It had, and still has, far better standards support than IE. IE isn't even anywhere near catching up to the other popular browsers in standards support.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
  3. Uhhh by Hassman · · Score: 4, Insightful

    No one else finds it odd that only a few browsers scored over 60%... What good is a standard that no one adheres to?

    Makes it seem more like a suggestion...

    --
    -Mark
    Dovie'andi se tovya sagain.
    1. Re:Uhhh by Hassman · · Score: 4, Interesting

      hah. not really.

      I just find it very amusing. We have 'standard' that no one really follows. When the best score is a 90% from a browser that probably is the lest supported in terms of actual web sites, and the next couple that come it are at 70% or so. That is like a C- with no curve. Not exactly worthy of bragging...

      It just makes me wonder what all the fuss is about.

      --
      -Mark
      Dovie'andi se tovya sagain.
    2. Re:Uhhh by xZgf6xHx2uhoAj9D · · Score: 3, Insightful

      The Acid tests are, to put it kindly, perverse. They basically try to hit every corner case of the standards in the most convoluted way possible. I'm not saying 60% is adequate, but it's understandable for a browser that's under development.

    3. Re:Uhhh by The+Ancients · · Score: 4, Informative

      You're confusing intent with result.

      The difference is that the teams working on Safari, Opera, Firefox, et al want to improve their product. Microsoft didn't care for a very long time. In fact, the Safari team even have a bug filed for the rendering issues Safari has with Acid3. Further, they're communicating frequently with their user base and anyone else interested with regard to their progress.

    4. Re:Uhhh by Shados · · Score: 2, Informative

      On Slashdot, you keep hearing about "This is the standard!!!", but the W3C and other such entities do not make standards. They propose standards. Then the market decides if it wants it or not. Since a lot of bodies don't have the time or manpower to make anything better (and even if they could, it would be quite a waste of time and money), they take what the W3C spits out and implement it. As good a spec as any. And -then- it becomes the standard. Stuff like Acid Test helps meet that goal.

      That being said, as time went on, the W3C really started spitting out real crap, so I'm not sure that its such a good goal to have... As opposed to standards like WS-I, which represents the real world and really do help on a day to day basis.

    5. Re:Uhhh by pembo13 · · Score: 3, Informative

      Not really. I often hear/read of browsers degrading compliance for the sake of rendering what would otherwise work only in IE.

      --
      "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
    6. Re:Uhhh by mike_sucks · · Score: 4, Insightful
      You're right, they aren't standards. Go to any one of the W3's "standards" documents and you'll see they are all called "Recommendations", HTML 4.01, for example. The cool kids call them "RECs".

      Now, what good is a recommendation, you ask? Plenty - mostly interoperability. The W3C provides a specification and recommends people implement it. Those that do can interoprate. The consumer wins.

      How do you get the vendors to implement the RECs? Make it an important bullet point on their feature lists. The Acid tests are a particularly well done kick in the backside for browser vendors. They have effectively become more important than the bullet point that says "standards compliant" because they are a (limited) test suite. For vendors to be able to say they do well in the tests, certain key parts of the RECs must be implemented and done so correctly, there is no room for buggy or partial implementation.

      The result in the end is better interoperability. The RECs provide that common basis that vendors can't quibble over. The Acid tests are both the carrot to get them implementing the RECs and proof that they did so (partially) correctly.

      /Mike

      --
      -- "So, what's the deal with Auntie Gerschwitz et all?"
    7. Re:Uhhh by Bogtha · · Score: 4, Informative

      Since a lot of bodies don't have the time or manpower to make anything better (and even if they could, it would be quite a waste of time and money), they take what the W3C spits out and implement it.

      That's not really true. Browser vendors participate in the W3C working groups that publish these specifications. They have an active role in creating them. Take a look at the acknowledgment section of the CSS 2 specification, for example.

      This specification is the product of the W3C Working Group on Cascading Style Sheets and Formatting Properties. In addition to the editors of this specification, the members of the Working Group are: Brad Chase (Bitstream), Chris Wilson (Microsoft), Daniel Glazman (Electricité de France), Dave Raggett (W3C/HP), Ed Tecot (Microsoft), Jared Sorensen (Novell), Lauren Wood (SoftQuad), Laurie Anna Kaplan (Microsoft), Mike Wexler (Adobe), Murray Maloney (Grif), Powell Smith (IBM), Robert Stevahn (HP), Steve Byrne (JavaSoft), Steven Pemberton (CWI), Thom Phillabaum (Netscape), Douglas Rand (Silicon Graphics), Robert Pernett (Lotus), Dwayne Dicks (SoftQuad), and Sho Kuwamoto (Macromedia). We thank them for their continued efforts.

      A number of invited experts to the Working Group have contributed: George Kersher, Glenn Rippel (Bitstream), Jeff Veen (HotWired), Markku T. Hakkinen (The Productivity Works), Martin Dürst (W3C, formerly Universität Zürich), Roy Platon (RAL), Todd Fahrner (Verso), Tim Boland (NIST), Eric Meyer (Case Western Reserve University), and Vincent Quint (W3C).

      The section on Web Fonts was strongly shaped by Brad Chase (Bitstream) David Meltzer (Microsoft Typography) and Steve Zilles (Adobe). The following people have also contributed in various ways to the section pertaining to fonts: Alex Beamon (Apple), Ashok Saxena (Adobe), Ben Bauermeister (HP), Dave Raggett (W3C/HP), David Opstad (Apple), David Goldsmith (Apple), Ed Tecot (Microsoft), Erik van Blokland (LettError), François Yergeau (Alis), Gavin Nicol (Inso), Herbert van Zijl (Elsevier), Liam Quin, Misha Wolf (Reuters), Paul Haeberli (SGI), and the late Phil Karlton (Netscape).

      The section on Paged Media was in large parts authored by Robert Stevahn (HP) and Stephen Waters (Microsoft).

      Robert Stevahn (HP), Scott Furman (Netscape), and Scott Isaacs (Microsoft) were key contributors to CSS Positioning.

      And of course, one of the four editors of the specification is Håkon Wium Lie, CTO of Opera.

      So you see, far from the poor old browser vendors not having the resources to make anything better and passively reacting to anything the W3C says, you can see that the browser vendors are substantially the people who made the specifications.

      --
      Bogtha Bogtha Bogtha
    8. Re:Uhhh by Bogtha · · Score: 2, Insightful

      Wait, so your argument is that it's only a standard if other people aren't allowed to participate, because they don't always agree with you?

      I don't think coming to a consensus is "like if they weren't participating because the result will be a big soup", I think it's the whole point of authoring standards.

      --
      Bogtha Bogtha Bogtha
    9. Re:Uhhh by Blakey+Rat · · Score: 4, Insightful

      Netscape/Mozilla also "didn't care" for a long period of time... that multiple-year-long slog between Netscape 4 and Mozilla 6 during which they didn't release a browser whatsoever. Of course, Microsoft does that between IE 6 and IE 7 and it's a horrible crime against humanity, but when Netscape/Mozilla did it, it's all OK.

      Microsoft stopped development on IE because:
      1) They weren't charging any money for it,
      2) There was no feasible competition on Windows,
      3) It was definitely "good enough" and in some ways superior to competing browsers. (XMLHttpRequest was invented by Microsoft, you might recall.)

      Considering that IE and Netscape were both pretty much just pulling "standards" out of their ass in the early days, the only reason Mozilla browser are more standards-compliant now is that they shredded the Netscape 4 code and started from scratch. IE is IE because, at the time this code was being written, the "standard" was "what Netscape did."

      All I can say is that I hope HTML5 starts hitting browsers soon... HTML5 is the first Internet standard designed by people who know what people actually use the web for.

      (CSS is supposed to be a language to describe page layout. And yet, it has no support for columns until CSS3. It took THREE VERSIONS to come up with a layout idea that's been used in newspapers for books for literally centuries?! This is a language designed by people amazingly removed from reality. And that's just one example of the idiocy of web standards.)

    10. Re:Uhhh by Bogtha · · Score: 4, Insightful

      Netscape/Mozilla also "didn't care" for a long period of time... that multiple-year-long slog between Netscape 4 and Mozilla 6 during which they didn't release a browser whatsoever. Of course, Microsoft does that between IE 6 and IE 7 and it's a horrible crime against humanity, but when Netscape/Mozilla did it, it's all OK.

      They aren't even remotely the same actions. Microsoft disbanded the Internet Explorer development team and assigned the developers to different projects. Netscape/Mozilla.org decided to invest extra time rewriting things to get a better end result. I personally think that was a bad investment, but that doesn't mean they killed the browser market and stopped development.

      IE is IE because, at the time this code was being written, the "standard" was "what Netscape did."

      Actually, Microsoft had a head-start with CSS because Netscape bet on JSSS. The W3C subsequently chose to reject JSSS in favour of CSS, meaning that while Microsoft released Internet Explorer 3 with preliminary CSS support, Netscape scrambled to transcode CSS to JSSS so that Netscape 4 had some kind of CSS support.

      So far from the standard being "what Netscape did", it was actually the other way around. The reason why Microsoft is so far behind is entirely their own doing.

      All I can say is that I hope HTML5 starts hitting browsers soon... HTML5 is the first Internet standard designed by people who know what people actually use the web for.

      Ahh yes, HTML 5, complete with the <font> element type. Because they know what people actually use the web for.

      It took THREE VERSIONS to come up with a layout idea that's been used in newspapers for books for literally centuries?!

      Web pages have infinite vertical space. Newspapers and books don't. Horizontal space is at a premium for web pages. It's not as important for newspapers and books. Unsurprisingly, a layout strategy that trades horizontal space for vertical space isn't a high priority for a technology primarily aimed at web pages. I wouldn't say that web standards that actually prioritise the web are nothing but "idiocy", I'd say that's entirely sensible.

      --
      Bogtha Bogtha Bogtha
    11. Re:Uhhh by Blakey+Rat · · Score: 2, Insightful

      I agree with your assertion that Netscape/Mozilla floundered for a few years
      But I certainly would'nt say that they "did'nt care" . Netscape (the company) was essentially getting squeezed illegaly by Microsoft and had bigger problems to worry about


      Oh please. They couldn't stand the heat, so they got out of the kitchen. Netscape wasn't being "illegally squeezed" by Microsoft, their product just sucked and they couldn't compete. Let's assume Dell got the choice to ship both Netscape 4 and IE 4 with Windows; which one would they make the default? The slow bloated one which crashed every hour, or the slim fast one which was perfectly stable?

      They made dumb decisions, like "let's stop making a browser, and start making a Communicator! With email and chat built-in!" Then they made those dumb decisions dumber, "let's sell our Communicator to corporations as a groupware solution!" All the while never fixing any of the fundamental bugs in the product.

      And when they lost marketshare, they still didn't fix their product, instead they went whining to the court about how "oh Microsoft's so unfair! Waaah!" You know what other company did the same thing? SCO. Of course, SCO is hated here because it sued Linux, and Netscape is loved because it sued Microsoft, but the situation is exactly the same.

      And about Mozilla I'd say they care too, because all the while that Microsoft sat idle, Mozilla managed to form an organization, develop a community and release a browser that captured double digit marketshare.

      I already explained why Microsoft sat idle. It's because they had no economic or technical reason to continue development, and Microsoft isn't run by idiots the way Netscape was. And yes, Mozilla has a double-digit marketshare, but only after they *finally* (after, what, 7-8 years?) gave up on that moronic "Communicator" idea and built *just a browser*. You know, the thing Netscape should have done in version 3.

      And while Firefox does happen to have a double-digit market share, barely, IE 7 is a better browser IMO. It's faster, more secure (on Vista, where it runs in a sandbox, I can't speak for XP), uses less memory, and has the same tabbed interface. Both FF and IE crash about the same amount of the time, but IE handles abusive CPU-sucking JS and Flash much better. And IE has the other 85% of the market.

    12. Re:Uhhh by Blakey+Rat · · Score: 2, Insightful

      I personally think that was a bad investment, but that doesn't mean they killed the browser market and stopped development.

      Well, when there's no competition, there's no development. That's true in almost every industry during all of history. That's why monopolies are so bad in the first place. And by taking their ball and going home, Netscape was handing Microsoft the monopoly in this area.

      (Of course, Netscape was run by absolute morons, and by the time IE was technically superior, Netscape was a lost cause. It's a pity they didn't, instead of engaging in pointless legal action, try to re-organize themselves and get some actual talent in-house.)

      BTW, Microsoft's bundling wasn't the reason Netscape bought it. Apple bundled both, and Macintosh users almost universally chose IE over Netscape. IE was just plain a better browser.

      Ahh yes, HTML 5, complete with the element type. Because they know what people actually use the web for.

      FONT is simple and it works, and does exactly what it looks like it does. So is CENTER, for that matter. Of course the validater is going to scream and whine at you for using it, but every web browser on Earth renders it fine, so who gives a crap what the validater says?

      They've spent the last decade on a pointless crusade for making web pages easier to read for machines. Except:

      1) The machines can't be simplier, because they still have to render HTML 4 pages anyway. There's no reason to believe, especially in 2008, that XHTML strict will catch on to the point where browsers can ditch HTML rendering.

      2) Web pages are written by human beings, human beings who aren't as good at machines at reading XML. Since the difference between XML and HTML in the browser is on the order of milliseconds, why not save the human being writing the code some time by making it easier?

      XHTML is throwing the baby out with the bathwater. C++ developers almost universally agree that goto shouldn't be used, and yet somehow they still manage to use C++ without whining about it-- even though it has goto in the spec! If you don't like the FONT tag in HTML5, well, don't use it. And don't use the CENTER tag, and don't use all those other tags you think are so horrible. Be like the C++ developer and, zen-like, remain calm in the face of "stuff in the language you don't like."

      Web pages have infinite vertical space. Newspapers and books don't.

      This is an example of exactly what I'm talking about. The vertical space above-the-fold is many times more valuable than the space below-the-fold. (The "fold" being declared as the point below which the average user is required to scroll.) If the W3C spent 5 minutes talking to actual web designers or web developers, they'd know that.

      While technically, you're correct, practically you're way wrong. Columns let a site maximize its above-the-fold space, making it more usable and more appealing to the end-user.

  4. Re:IE8 Beta 1? by MightyYar · · Score: 5, Informative

    Why has there been no discussion on Slashdot of IE 8 beta 1? Like, say, a front-page story from four days ago? :)

    It even has your same link right in the summary...
    --
    W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
  5. Re:IE8 Beta 1? by jsse · · Score: 5, Funny

    Dear customer, We regret the shortcoming that you found regarding ACID 3 test results of IE8. Please note that it's still in its beta stage and we'll put all the efforts in making IE8 score below its proud precedences, IE5.5, 6 and 7, before its release! Stay tune. We've never failed before, we won't fail this time. Yours truly, Department of Embracing Standards and Compatibilities, Microsoft.

  6. Summary answers its own question by Brett+Buck · · Score: 4, Funny

    They ALL score less than 20. That's essentially random response to the test - so it's just a matter of luck if one scores better than another.

            Brett

  7. Old Web Browser Standards by EEPROMS · · Score: 4, Insightful

    To put it all into perspective how bad IE 8.0 is when it comes to web standards I tested a two year old install of Konqueror (KDE 3.4) and it gets a score of 51%. The best IE 8.0 can do is 17%.

    1. Re:Old Web Browser Standards by John+Hasler · · Score: 4, Funny

      I don't think that release has arrived yet.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  8. Re:And older firefox versions do better too by Samari711 · · Score: 5, Insightful

    a beta version having worse performance than a production version isn't exactly the same as an ancient, no longer supported version having better performance than the current production version.

    --

    I never said I was smart, I just said I was smarter than you

  9. Re:And older firefox versions do better too by bunratty · · Score: 5, Informative

    Actually, according to multiple sources, Firefox 2.0.0.12 score 50%, lower than Firefox 3 builds. No, the quality of Firefox is not decreasing.

    --
    What a fool believes, he sees, no wise man has the power to reason away.
  10. Three months later by Anonymous Coward · · Score: 5, Funny

    Dear Customer,

    We regret to hear of the shortcoming you found in ACID 3 Test Home Basic. We have not forgotten our advertised promise to pass the test. On that note, we are proud to introduce the ACID 3 Test Pro! IE8 happily passes this version of ACID 3, which is comprised of VBScript, ActiveX, and Silverlight technologies.

    Yours Truly,
    Department of Extending Standards and Compatibilities
    Microsoft

  11. safari by sentientbrendan · · Score: 4, Interesting

    really seems to be kicking ass at 90%; granted it is from a nightly build and not an official release.

    Still, Safari seems to have been ahead of the game on standards and features for a while. Weren't they the first ones to pass acid2? Also, they were the first to implement various extensions to HTML which have become prevalent, such as the CANVAS tag, which was later added to firefox and others.

    Now, there's a version of safari for windows that I've been meaning to try, but it seems to still be in public beta, and has been there for quite a while. My question for anyone in the know, is whether the safari windows build is still progressing.

    1. Re:safari by bunratty · · Score: 5, Insightful

      Safari development builds are doing well on Acid3, and Safari passed Acid2 quickly, because Safari developers fixed the problems that the Acid tests demonstrate. If you look at the stable release builds of Safari, they do far worse than the stable release builds of Opera and Firefox. But if you look at the latest development builds, Safari does far better than Opera and Firefox. Safari is doing well on Acid tests because the developers put a lot of effort into making Safari do well on Acid tests, not because Safari is "ahead of the game" on standards.

      There's far too much bickering about which browser is best and which browser is behind the curve. It seems that Safari, Opera, and Firefox are all very good browsers each with their own strengths in standards compliance and user interface, with IE constantly playing catch-up.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    2. Re:safari by Idiot+with+a+gun · · Score: 3, Informative

      I would like to point out that Safari's HTML renderer, Webkit, is indeed open source.

    3. Re:safari by 99BottlesOfBeerInMyF · · Score: 4, Informative

      Safari development builds are doing well on Acid3, and Safari passed Acid2 quickly, because Safari developers fixed the problems that the Acid tests demonstrate. If you look at the stable release builds of Safari, they do far worse than the stable release builds of Opera and Firefox.

      I think your idea here is a bit off. The stable version of Safari does perform more poorly than the stable versions of Firefox and Opera, but I think this is more likely attributable to Apple's more leisurely release schedule. The article referenced here was obviously put together by someone more focused on Windows and OS X. They only tried to test one browser on one version of Linux, compared to the dozen or so for the other OS's. It is, then, understandable that you would get that impression from the data presented. What a lot of people forget is that Safari uses the Webkit rendering engine which is also used in a variety of other browsers whose developers also contribute to it. The stable version of Konquerer 3.5.8 uses the same rendering engine and scores a 52 on the Acid 3 test, better than either Firefox or Opera. So Webkit is being updated and did, in fact, do better than Gecko or Presto for stable release versions when Acid 3 was published. (Note Konquerer 4.0.2 scores a 62, but I don't know if that is considered a "stable" branch.)

      Mind you, this is not to imply that the Acid 3 test can really judge the respective compliance of the engines in general. This is not the case. The test was designed with bias in mind, bias against Webkit and Gecko. The criteria for inclusion in the test was that one or the other had to fail it and we don't know how many of the Acid 3 authors were focusing on one engine or another. If anything Opera and IE should be doing better than Firefox or Konquerer or Safari, since there are probably a number of tests those browsers fail, but which were excluded from Acid 3 simply because both the Gecko and Webkit engines passed it.

      Safari is doing well on Acid tests because the developers put a lot of effort into making Safari do well on Acid tests, not because Safari is "ahead of the game" on standards.

      I know for a fact that developers of both Gecko and Webkit are specifically using these tests as a way to find problems to fix, which is great since that is why the tests were written; not to try to measure "compliance."

      There's far too much bickering about which browser is best and which browser is behind the curve. It seems that Safari, Opera, and Firefox are all very good browsers each with their own strengths in standards compliance and user interface, with IE constantly playing catch-up.

      This is true enough, well except about IE maybe. In my own personal experience every browser other than IE works just fine for rendering everything I create to the standards. There might be the occasional bug or edge case, but I never run across them. IE, on the other hand, I have to create work arounds every single time. I'm not sure it is "playing catch up" so much as deliberately failing to implement huge portions of many standards as a way to prevent cross platform compatibility and keep Web applications that undermine their platform lock-in from being a real threat.

    4. Re:safari by Koiu+Lpoi · · Score: 3, Insightful

      Safari is doing well on Acid tests because the developers put a lot of effort into making Safari do well on Acid tests, not because Safari is "ahead of the game" on standards.
       
      Are these really different? The Acid Tests test standards compliance, so if you do well on them, even if it is your aim to do so, aren't you embracing standards?

    5. Re:safari by m50d · · Score: 4, Insightful

      Well yes, but the Acid Tests can't and won't test *all* standards. So it's a question of whether and how much you prioritize those particular standards over other, possibly more important (whatever that means) ones.

      --
      I am trolling
  12. Yes, you don't get it. by Belial6 · · Score: 5, Insightful

    I would have to say that it is that you don't get it. No one is so arrogant as to think that they can sit down and design the perfect web. As with virtually all of human achievement, we expect that there will be continual advancement, and hopefully we will never hit a wall. The Acid tests are road marks on the advancement of web browsers. The Acid tests are for the purpose of seeing just how compatible the browsers are. Scores of 0% and 100% are both useless. So, you make a test that is not so hard that no one can get even 1%, and that are not so easy that everyone gets 100%.

    Well, the browsers are getting to that 100% point. Acid2 was not built to check 100% compliance, at that would have been useless. Not that the main browsers are reaching 100%, Acid2 is becoming useless, and Acid3 is necessary to see who has the best compliance. To use your school analogy, consider Acid2 to be the second grade. It is important to achieve that level, but when you do, you can expect the 3rd grade to follow it.

    (And if your opinion of public schools is as low as mine, you are welcome to substitute "second grade" with level of knowledge that a 7 year old should have.

  13. Maybe this is obvious but... by JimboFBX · · Score: 5, Interesting

    If there doesn't exist a program that can render your test correctly, then how do you know for sure you wrote it correctly to begin with?

    1. Re:Maybe this is obvious but... by bunratty · · Score: 4, Informative

      You don't. On the other hand, if there is a flaw in Acid3, it will be found as the developers of web browsers attempt to pass it. Safari developers found a flaw in Acid2.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
  14. Re:Celik Strikes Back by Bogtha · · Score: 4, Informative

    wasn't IE 5.5 written with code which came over from IE5 for Mac, the first really well done major browser with nice CSS support?

    No, it wasn't. Internet Explorer 5.x for Windows uses the Trident rendering engine. Internet Explorer 5.x for the Mac uses the Tasman rendering engine. They are totally different codebases.

    which MS dumped when building IE6 for Win, because they could have their flagship internet browser rendering better on those other guy's OS and not their own.

    Actually, in most ways, Internet Explorer 6 has better standards support than Internet Explorer 5.x for the Mac.

    --
    Bogtha Bogtha Bogtha
  15. Re:Simple answers for simple questions by bunratty · · Score: 4, Informative

    The 100 subtests are nearly independent of each other. It's possible for a browser to fail a subtest simply because it failed an earlier subtest, but failing one subtest is not going to make a browser skip a major portion of the test. You can click on the A in Acid3 after the test is completed to see a report of exactly which tests failed.

    --
    What a fool believes, he sees, no wise man has the power to reason away.
  16. Re:And older firefox versions do better too by klui · · Score: 4, Informative

    Windows 2003: 2.0.0.12 = 51%; 3.0 beta 3 (portable version) = 58% here.

  17. Re:IE8 Beta 1? by Bogtha · · Score: 5, Informative

    It is a problem, but it's not the hard-coding people seem to think it is. The problem is not that Internet Explorer 8 is checking for www.webstandards.org, the problem is that the mirrors that are failing are changing the test in a way that is important to Internet Explorer. Part of the test refers to a page that intentionally doesn't exist in order to check a fallback option. The trouble is that this page is referred to with an absolute URL, which means that when you simply copy the test to another host, it becomes a cross-domain issue.

    Ian's pointing out that it's still a failure so it should be subject to the same fallback, which is correct, but the important point is that it's failing to load in a different way to how it would on the www.webstandards.org host because the mirrors didn't take the cross-domain issue into account. I expect the final version of Internet Explorer 8 to correct this problem, but it's not at all a case of Microsoft attempting to "cheat", just an unfortunate coincidence.

    --
    Bogtha Bogtha Bogtha
  18. Re:And older firefox versions do better too by neunon · · Score: 5, Informative

    I don't know how, but I messed up when making the table. I reconfirmed the results with the ones I had written down and realized the Firefox 2.0.0.12 Mac OS X entry was incorrect. I've corrected the error. The actual value is 52%. So 3.0b3 is actually doing better than the current release. Sorry about that error. - Steven

  19. Re:IE8 Beta 1? by 99BottlesOfBeerInMyF · · Score: 5, Informative

    Why is this modded down to -1? I'm running IE8b1 right now and yes, it runs Acid2 completely.

    It was probably modded down because we've already had this discussion in three different articles over the last week. IE8 beta passes the Acid 2 test only when run on webstandards.org, but fails if you run it on almost any mirror. The discussion further continued with speculation that MS had hardcoded a workaround specifically for the test and was "cheating". This turned out to be untrue and the reason was that webstandards.org references a page that exists incorrectly but the mirrors reference a page that doesn't exist. Both cases should be handled, but IE8 beta fails on the latter.

    Probably people were modding the post down because it was factually incorrect. A better way to deal with the problem is probably to post a factual response, but several people have done so and those posts have not been modded high enough so that the facts are more easily read than the misleading evidence presented in the post you are asking about. Either that or a dozen people with mod points just groaned and thought, "do we have to go through all this again?"

  20. Re:You shouldn't be supporting standards by LanceUppercut · · Score: 4, Insightful

    Sorry, but this is just plain nonsense. It is like saying that C and C++ standards made programming easy. However, the truth is that even if you teach the whole world all the intricacies of C or C++, it still won't turn everybody into programmers.

  21. not like it matters by MSDos-486 · · Score: 2, Informative

    One of the primary components of the Acid test are to see if a browser will properly handle out of spec code.In this case "proper handling" means ignore it. IE is counter intuitive in this sense because it has facilities to "guess" what should happen.

    <rant>
    Today I was borrowing someones computer and i went on a few websites with IE. When they came back they were disappointed because all of the sites i went to messed up there "recently visited" listing in IE. They were frustrated that that there would have to manually type the URLs of the pages to go to. Then I introduced them to the wonderful world of Favorites/Bookmarks, something I learned about back in 97. Now when I was in High School i tested out of all the intro to computer courses in order to take programming, so can anyone tell me what they teach in these classes. I mean seriously. Sometimes it surprises me how little people know about computers. Maybe its because I grew up in a city whose major employers included HP, Oracle, and BAE Systems( who bought Sanders, the inventors of the Magnavox Odyssey) . So maybe I just used to most people having a general understanding. It seems when I went to college the average computer skill per person I associate with dropped.

    </rant>
  22. mirrors not introduce change by HeroreV · · Score: 3, Informative
    The mirrors did not introduce anything new. From the linked IEBlog:

    It's worth mentioning that although most sites allow navigation like http://webstandards.org/ (note: the no www) this is also considered a cross domain access as www.webstandards.org != webstandards.org. This will also cause us to fail the ACID2 test and render the picture that you see above. So please type www.webstandards.org!

    The test should work from http://webstandards.org/files/acid2/test.html and http://www.webstandards.org/files/acid2/test.html, but IE8 fails the first one. The mirrors might exacerbate the problem, but they certainly did not introduce anything that wasn't in the original test.

    However, it is true that this issue has nothing to do with hardcoding a certain URL and trying to cheat.
    1. Re:mirrors not introduce change by Bogtha · · Score: 3, Informative

      It's not an intentional part of the test, it's accidental, a side-effect of webstandards.org failing to canonicalise their hostnames. If you read the press release, it only refers to the www version and nowhere is the no-www version mentioned, nor is this issue brought up in the technical guide. If they were trying to include this in the test, they'd have picked a hostname foreign to both the www and no-www versions so that it failed reliably.

      --
      Bogtha Bogtha Bogtha
    2. Re:mirrors not introduce change by Bogtha · · Score: 2, Interesting

      But it was though. When you view the Acid test from the canonical address, there is no cross-domain request. When you view it from a mirror, there is. The fact that one of the mirrors happens to be webstandards.org is unimportant. That's not the publicised address for the test, it's an oversight that it's available from that URL at all. By making the unaltered HTML available on a host other than www.webstandards.org, the mirrors (including webstandards.org) are introducing a new factor into the test.

      --
      Bogtha Bogtha Bogtha
  23. Some insight regarding the Acid 3 Test by trixy_1086 · · Score: 5, Informative
    I found this information regarding the Acid 3 test on a Webkit developer's site (http://webkit.org/blog/158/the-acid-3-test/) As much as I hate to debunk any article bashing IE, here is the information from the article:

    If you run Acid 3 on the shipping versions of current browsers (Firefox 2, Safari 3, Opera 9, IE7), you'll see that they all score quite low. For example Safari 3 scores a 39/100. This percentage score is a bit misleading however. The situation with all four browser engines really isn't that bad. You can think of the Acid 3 test as consisting of 100 individual test suites. In order for a browser engine to claim one of these precious 100 points, it has to pass a whole battery of tests around a specific standard. In other words it's like the browser is being asked to take 100 separate exams and score an A+ on each test in order to get any credit at all. The reality is that all of the browsers are doing much better than their scores would have you believe, since the engines are often passing a majority of the subtests and experiencing minor failures that cost them the point for that section.
  24. Re:And older firefox versions do better too by edwdig · · Score: 4, Insightful

    Any browsers that came out before the Acid3 test was released are doing absolutely dismally.

    That's exactly the point of the Acid tests. They're designed to motivate browser developers by pointing out a lot of flaws in current implementations.

  25. Re:Why use IE?! by ledow · · Score: 2, Insightful

    I'm really not a Microsoft advocate but I work in Windows-only schools... I do completely understand the frustration but off the top of my head:

    1) Group Policy integration

    I can set browser settings (every single one that you see in IE's Internet options etc.) for a group of computers and fine-tune each setting to particular users. You don't want kids changing their proxy settings, you don't want them playing with trusted zones, you don't want them getting overwhelmed with dialogs when they log in for the first time. You don't want to have to set it up per-user.

    2) Content that is IE only.

    Everything is web-based nowadays. For instance, schools are pulling lesson plans, educational games, etc. off websites or "cached content" (i.e. stick a Linux box full of some companies flash-heavy website in your school and every month or so they'll update it for you... this is an actual product from several very expensive companies). Most of it works only in IE, although I have seen a few that will work on Firefox too. ActiveX is seriously over-used in the educational sector for example. And therefore if you want support (which schools in particular see as vital), you have to use IE.

    3) The little blue E

    Seriously, I have dozens of users (and I get more each year) who when they want the Internet go for the little blue E shortcut. I have actually replaced it with an identical-looking one that ran Firefox and only the "power-users" on the network actually noticed anything wrong. 450 kids just carried on working as if there was nothing different.

    As soon as everybody gets off their backsides and gives me non-IE support on all the content that the schools carry, I'd move every school over. The next hurdle after that is making it easy to customise every option on a per-user/per-computer basis properly. The third is easily overcome even if it is selling your soul to put a decent browser behind the IE icon...

  26. Sigh. by Xest · · Score: 2, Insightful

    This is similar to saying that MS-DOS 5 has less bugs than Windows Vista hence MS-DOS 5 is far better than Windows Vista

    Well yes, of course it has less bugs, because it's much smaller and supports far fewer features, but that doesn't make it better, it's nigh on useless for everything people want to do nowadays.

    At the end of the day, IE5.5 supports less features and gracefully falls back where it fails on a feature as it should. IE6 and IE7 are much more ambitious and implement far more features, but when pushed to the limits on these features they fail more horribly than IE5 which doesn't even try. There is an argument that features shouldn't be implemented at all if they don't work perfectly but I disagree, the fact is the features in question almost certainly work in say 90% of cases it's just that Acid3 is specifically exploiting the cases where it doesn't work rather than where it does.

    People are free to stick with IE5.5 if they like the fact it does better on the Acid3 test if they want, but don't come crying when you can't use half the features on sites that are designed for the new series of browsers.

    Acid3 is doing it's job well, it's highlighting problems in implementations so that they can be fixed in future versions. I'm not sure why some people see Acid tests as a tool to attack browsers with, that's not the purpose. Whilst crappy journalism might like to use it for this purpose one would hope that Slashdot was above Daily Mail type shoddy stories.

  27. Re:I tried IE8 beta on Windows Server 2003 SP#2 &a by dishpig · · Score: 2, Funny

    Thank you for submitting your resume. Unfortunately there are no positions currently available.