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.

308 comments

  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 hedwards · · Score: 0, Offtopic

      Acid? I'd have thought shrooms were more IE's style.

    2. Re:Read that too fast... by The+Ancients · · Score: 1, Funny

      IE6 and IE7 On Acid IE's recreational drug use would explain a lot...

      It would explain why developers for IE need drugs, as well.

    3. Re:Read that too fast... by poopdeville · · Score: 0, Offtopic

      I see them more as Ubuntu users because of all the brown, but you make an interesting point.

      --
      After all, I am strangely colored.
    4. Re:Read that too fast... by Mr_eX9 · · Score: 3, Funny

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

    5. Re:Read that too fast... by Anonymous Coward · · Score: 0

      whatever, listen to the man, but computing wouldn't be where it is today without lsd.

    6. Re:Read that too fast... by xushi · · Score: 0

      I'd like to know what browser the Acid 3 people used to render the resulting image for us...

    7. Re:Read that too fast... by ozmanjusri · · Score: 1

      A hand-coded version of Firefox hacked specifically to render Acid 3.

      --
      "I've got more toys than Teruhisa Kitahara."
    8. Re:Read that too fast... by ILongForDarkness · · Score: 1

      Don't you mean "you must be on ACID to use IE 6 or 7"? Kudos seem to go to Safari on this one, and I just started working at a Mac shop, yeah me :)

    9. Re:Read that too fast... by YttriumOxide · · Score: 1

      Staring at a monitor AT ALL while on Acid can be a fairly unpleasant experience - let's not make it worse by using IE!

      --
      My book about LSD and Self-Discovery
      Also on facebook as: DroppingAcidDaleBewan
    10. Re:Read that too fast... by Anonymous Coward · · Score: 0

      Obviously, it is the mods that are on drugs. That's why the parent is labeled "Offtopic."

      Stupid junkie mods.

    11. 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"
    12. Re:Read that too fast... by ozmanjusri · · Score: 1

      Because it's unlikely to render anything other than ACID 3 well. The hacks are specific to the test, not to the intent of the standard.

      --
      "I've got more toys than Teruhisa Kitahara."
  2. TheDailyWTF by calebt3 · · Score: 0, Offtopic

    This really belongs on thedailywtf.com

    1. Re:TheDailyWTF by calebt3 · · Score: 0, Redundant

      OK, it's submitted.

  3. 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 falcon5768 · · Score: 1

      got your browsers a bit mixed up there. IE 5.5 was in direct competition, 6 was released after the war.

      --

      "Slashdot, where telling the truth is overrated but lying is insightful."

    4. 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
    5. 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
    6. Re:Very simple by superpulpsicle · · Score: 1

      The browser war was so over years ago. The only reason why IE7 is still standing is because corporate apps are forced to support it as M$ has far more corporate influence than mozilla org.

    7. Re:Very simple by R.Mo_Robert · · Score: 1

      Internet Explorer 6, when it was released was probably the best browser around when it came to supporting CSS.

      Err, pretty sure I was using Mozilla back in 2001 when IE 6 was released (it was in the 0.9 versions at this time), and I'm sure it had better standards support than any version of IE did until recently.

      --
      R.Mo
    8. Re:Very simple by Bogtha · · Score: 1

      I don't think it's fair to count pre-beta software. I remember the quality of Mozilla 0.9 and I distinctly remember choosing Netscape 4 over it. Sure, it supported more CSS, but it was hardly an option for the average person. If it's important, consider my previous statement to be "best released browser around".

      --
      Bogtha Bogtha Bogtha
    9. Re:Very simple by Bill,+Shooter+of+Bul · · Score: 1

      I'm not taking that statement on faith. Everyone thought the entire Mozilla project was doomed to failure at the time. I remember trying to convince my employer at the time that our new project had to support netscape ( mozilla was always just supposed to become the next version of Netscape). But I lost that argument because it sucked, didn't support much css or work correctly with most websites in existence. Take a look at Joel's assessment of mozilla in 2003 when he first switched to firefox.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    10. Re:Very simple by JohnBailey · · Score: 1

      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. Only until the others get a significant if inferior market share. IE may have something around 70%, but companies selling stuff on the net don't want to dismiss a potential 30% of customers, and I would imagine that quite a few people decide to favor the non IE browsers out of dislike for Microsoft.
      It used to be the case that if you used Firefox, you also had to use IE for some sites. now, hardly at all. I came across one site, which was for a UK TV company that wouldn't work properly in Firefox, but it worked fine in sea monkey.

      The awkward thing about monopolies is that they have to keep fighting to keep their monopoly, or it disappears faster than one might think. Microsoft won the browser wars, but winning a war is easy. Occupation however is a completely different matter.
      --
      It is difficult to get a man to understand something when his job depends on not understanding it.
    11. Re:Very simple by Hyperspite · · Score: 1

      I feel deja vu. Didn't we have this argument before?

    12. 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.
    13. 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)
    14. 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?!
    15. Re:Very simple by DKlineburg · · Score: 1

      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

      I would have to agree. IE5.5 was probably closer to Internet standards. Than at some point in there history, Microsoft realized they had a large market share and switched there thinking. "We are the big guys, lets make everyone follow us." There next versions forced others to code to there form. This wasn't widely accepted, as havening to program twice aggravated a lot of coders. This is forcing Microsoft to go back the other way after breaking there code in the first place.
      --
      Memory is deceptive because it is colored by today's events. - Albert Einstein
    16. Re:Very simple by edwdig · · Score: 1

      I don't think it's fair to count pre-beta software. I remember the quality of Mozilla 0.9 and I distinctly remember choosing Netscape 4 over it.

      Mozilla 0.9 was far better than pre-beta. That's when it became a pleasure to use. The UI had just about worked the kinks out by then, and that's around when tabs came in.

      Mozilla 0.6 was the release Netscape 6 was based off of. Even then, it was a tossup whether it was better or worse than Netscape 4. It crashed less than Netscape and usually rendered a lot better (except for sites that sent it NS4 web pages), but the UI was very rough.

    17. Re:Very simple by edwdig · · Score: 1

      But I lost that argument because it sucked, didn't support much css or work correctly with most websites in existence.

      It certainly worked with most websites. The few it didn't were either detecting it as Netscape 4 and sending it the wrong HTML, or were coded to use IE only features instead of the standards. People just do less of those things today.

      Take a look at Joel's assessment of mozilla in 2003 when he first switched to firefox.

      He's ranting about Firefox having a ton of features that had been in Mozilla for years at that point. The only new things Joel listed was that FireFox copied IE's Alt-D keyboard shortcut, and they changed the default setting for the Ctrl-Enter option to match his preference.

      I think the NT authentication was relatively new then, but (a) it was in Mozilla first and (b) that's a really damn obscure feature, and one that I wouldn't expect non-MS products to support, so there's a limit to the validity of him complaining there.

    18. Re:Very simple by unapersson · · Score: 1

      Netscape 6 was based on Mozilla 0.9. So it was used in release software.

    19. Re:Very simple by Symbolis · · Score: 1

      Wasn't the pass done under a non-default mode?

      From webstandards.org:

      Note: When taking the test, you should use the default settings of the browser you are testing. Changing the zoom level, minimum font size, applying a fit-to-width algorithm, or making other changes may alter the rendition of the Acid2 page without this constituting a failure in compliance. (Added 21 July 2006)

      Or maybe I'm thinking of something else?

    20. Re:Very simple by LingNoi · · Score: 1

      oh wow! IE8 the browser that isn't even released yet passes Acid 2, oh wait no way to verify..

    21. Re:Very simple by PhireN · · Score: 1

      IE8 only passes the acid 2 test when the 404 page redirect thing is on the same domain as the test, otherwise it the eyes fail.

    22. Re:Very simple by that+this+is+not+und · · Score: 1

      Have the most popular browser and have it not be compatible, and you force everyone to be compatible with YOU -

      Indeed. That's a trick that Microsoft learned from Netscape, who aimed to control the market in servers by introducing proprietary tags and features in their (free) browser that only their (closed, expensive) server could dish out.

      It's by no means a unique tactic of Redmondware.

    23. Re:Very simple by Wildclaw · · Score: 1

      It most likely is the default settings.

      There was some debate a while ago by microsoft introducing the idea of having to mark standard pages with a special http header to trigger the new rendering mode, but they have backtracked and gone with a more sensible solution.

      The new (more correct) rendering mode is now the default, and you can now instead add a special http header to force the browser into the old redering mode with all its quirks.

    24. 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.
    25. Re:Very simple by remmelt · · Score: 1

      Keyword is "improve." One article described IE8 as being "standards-based", which is probably the best description.

    26. Re:Very simple by HeronBlademaster · · Score: 1

      It used to be the case that if you used Firefox, you also had to use IE for some sites. now, hardly at all. I came across one site, which was for a UK TV company that wouldn't work properly in Firefox, but it worked fine in sea monkey. The only site I use semi-regularly that doesn't work properly in Firefox is the MSDNAA site... but that's a Microsoft site, so I guess I shouldn't expect anything else.
    27. Re:Very simple by Bert64 · · Score: 1

      When IE6 was released, it had vastly inferior CSS support to version 5 on the mac.
      I heard there were plans to bring the rendering engine from the mac version over, and that these plans were abandoned when development on IE was found up...

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    28. Re:Very simple by tbannist · · Score: 1


      1) Because the ACID tests show clearly and concisely that it is Microsoft who is doing it wrong.
      2) Because Firefox has been eating into their market share.
      3) Because it's embrace and extend to extinguish the competition.
      4) Because the Acid tests won't check for new, non-standard features that Microsoft introduces (Hello Silverlight!)
      5) Because the Microsoft apologists who scream "It's Microsoft therefore it is the standard!" are ignored.
      6) Because people are starting to deploy advanced features that say "Doesn't work in IE. Try using a modern browser, please".
      7) Because being seen as the company with the worst web browser is bad for the Microsoft brand.

      I'm sure there are other reasons, but those are very good self interested reasons why Microsoft would want to implement the standards.

      --
      Fanatically anti-fanatical
    29. Re:Very simple by immcintosh · · Score: 1

      Maybe this is just me, but I'm pretty sure that deliberately halting development on your product is one of the best ways to sabotage its compatibility with future developments in the field. For people who aren't interested in splitting hairs, a choice to halt development is for all intents and purposes a CHOICE to avoid compatibility.

      You claim that they "delivered" on a call for improved standards support, but if the page linked in this article is to be believed, that simply isn't the case. Judging by the abysmal score linked in the summary, MS has done very little to improve overall standards compatibility. My guess, although somewhat naive from being based only on these numbers, is that all they did was fix the special cases that would allow them to pass Acid2, the fact of which is revealed by Acid3.

    30. Re:Very simple by Bogtha · · Score: 1

      Maybe this is just me, but I'm pretty sure that deliberately halting development on your product is one of the best ways to sabotage its compatibility with future developments in the field. For people who aren't interested in splitting hairs, a choice to halt development is for all intents and purposes a CHOICE to avoid compatibility.

      Please note the context of my comment. I wasn't pointing out Internet Explorer's improvements in standards support for the sake of it. Somebody claimed that the reason Internet Explorer 6 and 7 did worse than Internet Explorer 5.5 in the Acid3 test was because Microsoft deliberately sabotaged it. I pointed out that they actually improved standards support to debunk that conspiracy theory.

      Microsoft halting development simply isn't relevant in this context. So they halted development. So compatibility suffered as a result. That doesn't mean the lower scores of Internet Explorer 6 and 7 are a result of that. They can't be the result of that — no development was happening, so how could the score move in any direction at all?

      You claim that they "delivered" on a call for improved standards support, but if the page linked in this article is to be believed, that simply isn't the case.

      You misunderstand the purpose of the Acid tests. They are deliberately constructed to highlight flaws in popular browsers. You can't really use the score to judge browsers in the way you are. You can use them as a gauge to see how well a vendor is addressing the issues over time, but the scores are pretty independent between browsers due to the selection of tests.

      My guess, although somewhat naive from being based only on these numbers, is that all they did was fix the special cases that would allow them to pass Acid2, the fact of which is revealed by Acid3.

      No, that's not even remotely the case. The Acid tests don't work that way. Most of what Acid3 tests is not closely related to what Acid2 tests. As for special-casing the code, feel free to download the Internet Explorer 8 beta and check for yourself.

      --
      Bogtha Bogtha Bogtha
    31. Re:Very simple by Ilgaz · · Score: 1

      Here is why:

      http://www.opera.com/pressreleases/en/2007/12/13/index.dml

      Opera files antitrust complaint with the EU

      The complaint describes how Microsoft is abusing its dominant position by tying its browser, Internet Explorer, to the Windows operating system and by hindering interoperability by not following accepted Web standards. Opera has requested the Commission to take the necessary actions to compel Microsoft to give consumers a real choice and to support open Web standards in Internet Explorer.

    32. Re:Very simple by MattZ3 · · Score: 1

      Why is it that a "standards-based" browser that passes the Acid2 (like IE8) still doesn't render certain pages correctly, and others (like Opera, Firefox 3 Beta, etc.) do?

      try opening this link in IE8, then in another standards complaint browser. notice that IE8 doesn't display it right.
      http://www.windowsmarketplace.com/content.aspx?ctId=391

      weird, huh?

    33. Re:Very simple by dedazo · · Score: 1
      Opera is the least of Microsoft's problems right now.

      Oh, and this comes to mind as well. Opera's biggest enemy is not IE, it's Firefox.

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    34. Re:Very simple by jhol13 · · Score: 1

      No, IE does not try to be compliant.

      It tries to pass the tests so Microsoft can claim "compliance". The difference is huge, and we all know it.

    35. Re:Very simple by jhol13 · · Score: 1

      If IE tries to be compatible, not just pass one single test (Acid2), why it does so badly on Acid3?

      I do not believe Microsoft has ever responded to "improved standards support", only smoke and mirrors. Passin a single test is not IMNSHO "delivered on".

    36. Re:Very simple by arotenbe · · Score: 1

      IE8, when released, will pass the Acid2 by default. Since Microsoft agreed to get rid of the mandatory switch for enabling standards mode, any page with a proper DOCTYPE will render in IE8's most standards-compliant mode by default. In other words, IE8 will act like every other browser.

      --
      Tomato wedge sperm darts that are Republican.
    37. Re:Very simple by Bogtha · · Score: 1

      If IE tries to be compatible, not just pass one single test (Acid2), why it does so badly on Acid3?

      Please try to keep up with the conversation. As has been explained many, many times in the comments here, Acid3 is deliberately constructed to highlight problems in popular browsers. All browsers do badly on Acid3, no matter how well they did with Acid2. There'd be no point in constructing an acid test that browsers did well on.

      Passin a single test is not IMNSHO "delivered on".

      No, it's not. The improved standards support, which you can verify for yourself, is "delivering on". The Acid2 test being passed is just an example of the improved standards support.

      If you are so concerned about tests, why not try the W3C CSS test suites? Or why don't you check out the 700 new tests that Microsoft is contributing?

      Face it, Microsoft is improving interoperability and support for standards with their work on Internet Explorer. Regardless of your opinion of them, you cannot deny this.

      --
      Bogtha Bogtha Bogtha
  4. IE8 Beta 1? by Ai+Olor-Wile · · Score: 0, Troll

    Why has there been no discussion on Slashdot of IE 8 beta 1?

    Available here without any WGA crap.

    (It gets 10/100, btw, and can't do Acid2 completely.)

    1. 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.
    2. 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.

    3. Re:IE8 Beta 1? by canuck57 · · Score: 0, Troll

      Why has there been no discussion on Slashdot of IE 8 beta 1?

      Might be because most who have tried IE 7, don't take IE 8 seriously and have switched to Firefox.

      Not a joke either. Some people at work are using Vista with IE 7. The site fails, we tell them to use Firefox and it authenticates them and works well. Problem solved.

      Thinking about scraping Vista myself, even though Firefox and Open Office works, too many quirks with it. Took me 3 hours to hack it to work with Samba.

      It is true though, Vista is more secure out of the box, because nothing works.

    4. Re:IE8 Beta 1? by bunratty · · Score: 1

      [IE8] can't do Acid2 completely.
      Yes it can. I just checked.
      There's a problem when you run the Acid2 test in IE8 Beta 1 from a website other than www.webstandards.org. Ian Hickson, who developed the Acid2 test, apparently says that IE8 Beta 1 fails Acid2 because of this flaw.
      --
      What a fool believes, he sees, no wise man has the power to reason away.
    5. Re:IE8 Beta 1? by Schnapple · · Score: 1

      [IE8] can't do Acid2 completely.
      Yes it can. I just checked.
      Why is this modded down to -1? I'm running IE8b1 right now and yes, it runs Acid2 completely. In fact, it does it better than the currently released 2.x version of Firefox. Perhaps the moderators are still on the outdated information that IE8 requires the meta tag for Standards Mode? Microsoft changed their tune on this so now IE8b1 is in standards mode by default. If you still don't think IE8 passes Acid2 then explain why.
    6. 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
    7. Re:IE8 Beta 1? by Anonymous Coward · · Score: 1, Funny

      Oooh, can we get some ice for that BURN?

      </highschool>

    8. 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?"

    9. Re:IE8 Beta 1? by Anonymous Coward · · Score: 0

      It's just like OpenBSD then?

    10. Re:IE8 Beta 1? by nstlgc · · Score: 1

      Yes. Slashdot is NOT the place for having the same discussion over and over and over again.

      Lol. Fucken nazis!

      --
      I'm Rocco. I'm the +5 Funny man.
    11. Re:IE8 Beta 1? by pklinken · · Score: 1

      Colonel Cargill, is that you ?!

    12. Re:IE8 Beta 1? by Anonymous Coward · · Score: 0

      No, they're completely different. For example, Netcraft has not yet been able to confirm rumors of Vista's demise.

  5. IE 5.5 Beats 6 and 7 by MidnightBrewer · · Score: 0, Troll

    I guess it just goes to show you that two wrongs do make a right. IE's abilities to render a web page reliably go so far into the realm of incompetence that they've gone straight through and come out the other side.

    --
    "Give a man fire, and he'll be warm for a day; set a man on fire, and he'll be warm for the rest of his life
  6. Celik Strikes Back by richdun · · Score: 0

    That "C" should be the one with the little squiggly on the bottom. I'm sure I can find it in my character map, but don't want those without a Unicode compliant browser to see some Chinese character or something... since we are talking the various iterations of IE here.

    IIRC, and someone with a better degree in Web History can probably elaborate, but 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? Tantek Celik was lead (or close to lead) on that, and set the pace for good CSS compliance... 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.

    1. 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
  7. 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 dagamer34 · · Score: 1

      It's designed so that no browser as 100% because they ALL have work to do in complying with the latest standards out there for web development. Specifically however, the Acid tests are a bitch because they test purposefully incorrectly written code and expect a certain "defined" result. Then again, standards are standards.

    2. 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.
    3. 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.

    4. 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.

    5. Re:Uhhh by Gyga · · Score: 1

      What schools do you go to? A 70% is a D- a 69 is an F. A 90 is a B. No one is doing good. BLAME THE TEACHER ... I mean standard.

      --
      I don't preview or spellcheck.
    6. Re:Uhhh by MidnightBrewer · · Score: 1

      Wow, I got scored as a troll? That's a first. Come on, guys, I meant it as humor, tongue-in-cheek kind of thing. Note the title of my comment; I was referring to IE 5.5 *specifically* as getting things right by dint of its crappiness. I'm sorry, but it's a well-documented fact that it has a horrible render engine chock-full of bugs. As a web developer, I've earned the right to say that the browser has its problems.

      I have to say that 7.0 is a lot easier to code for and seems to actually be respecting my CSS. Of course, I still have to go back and tweak things to work under 6.0, because it fails to render the page correctly.

      Anyway, I also know what the Acid test is for, and that it represents everything you can get wrong in web page coding. It's a measure of how well a render engine can stand up to the worst conditions, not how well it can deal with properly written code.

      --
      "Give a man fire, and he'll be warm for a day; set a man on fire, and he'll be warm for the rest of his life
    7. 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.

    8. 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
    9. Re:Uhhh by calebt3 · · Score: 1

      Methinks you hit the wrong "Reply To" button...

    10. Re:Uhhh by Kjella · · Score: 1

      Yes, because they should implement it first and write the design documents later like in the lesser known waterclimb method. Eventually you get to the requirements phase, where you tell the customer what's required of him to use the product. This also saves the overhead of the verification phase, because clearly whatever the code does is what it was meant to do and only the documentation can be imperfect. By the time you've reached the maintenance phase, you have hopefully been promoted and can blame it all on your less gifted successor. What's disturbing is that I suspect this method is actually in widespread use.

      --
      Live today, because you never know what tomorrow brings
    11. Re:Uhhh by Anonymous Coward · · Score: 0

      This is how it worked where I went to school: A: 100-90% B: 89-80% C: 79-70% D: 69-60% F: 59% and lower

    12. 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?"
    13. 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
    14. Re:Uhhh by Anonymous Coward · · Score: 0

      That or he uses multiple accounts, and he really is a troll.

    15. Re:Uhhh by hedwards · · Score: 1

      But, the markets haven't been creating standards. If the markets were creating them, then there'd be consistency. The fact that IE alone can't be reliably render pages that use current technology is a pretty good indication that the markets haven't been creating standards.

      Hence why people are willing to push for the w3c recommendations, at least those are easily read and understood. And why better browsers aim towards complying with the recommendations rather than each other.

      Market based solutions for technological problems rarely work out in a way that is desirable, or even predictable.

    16. Re:Uhhh by Vexorian · · Score: 1

      Who is this "no one" guy?

      It is a new test for a reason, you know?

      I am a little annoyed by the fact it looks like in order for your browser to be standard compliant you now need to enable javascript...

      --

      Copyright infringement is "piracy" in the same way DRM is "consumer rape"
    17. Re:Uhhh by Shados · · Score: 1

      A big group of people who disagree with each other. Its like if they werent participating, because the result will be a big soup of everyone's idea... so the entity may as well be separate. (Its a big complain about the W3C from its own members, thus why you see things like HTML5 pop up)

    18. Re:Uhhh by impactor · · Score: 1

      Correction, No one is doing well. At my school less then 50 is a fail, above 80 is an A.

    19. 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
    20. Re:Uhhh by MidnightBrewer · · Score: 1

      Figures. Ah well, can't always be right...

      --
      "Give a man fire, and he'll be warm for a day; set a man on fire, and he'll be warm for the rest of his life
    21. 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.)

    22. Re:Uhhh by watzinaneihm · · Score: 1

      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, this went on till they gave up and gave whatever remained to the community. I'd say they did care based on their decision of opening the product up.
      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.

      --
      .ACMD setaloiv siht gnidaeR
    23. 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
    24. Re:Uhhh by Spy+der+Mann · · Score: 1
      On Slashdot, you keep hearing about "This is the standard!!!"

      Hmmm that would make an excellent epic scene...

      IE: Compatibility? This is madness!
      Webstandards.org: Madness?
      This...
      is...
      STANDARDS!!!
      *Throws ie into the pit of Acid death*

    25. Re:Uhhh by jonaskoelker · · Score: 1

      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.
      Let's see.

      Yes, I agree: vertical space is infinite and horizontal space is limited. Going from there straight to "no columns" is pulling a fast one, though: lines of text are generally easier to read--in particular the \r\n is easier, ISTR--when lines are roughly 66 characters long [1]. It's generally desirable to have as much text on the screen as possible. The only way of doing both 66 chars/line and packing the screen is by having several lines be adjacent; that is, by doing columns.

      One problem of columns is of course that unless you specify Everything (TM), you don't know how tall it's going to be; as it's very desirable not to have to scroll upwards, you're somewhat in a pickle.

      I'm toying with an idea for what I think I want: an option for a text block (p or div, no?) that means "show the text as follows: create as many columns of 66-char lines that will fit horizontally, and make them so tall that they take up almost all the screen. Repeat this for any remaining text". That should give the best of all worlds, but there might be issues.

      [1] http://www.ctan.org/tex-archive/info/lshort/english/lshort.pdf, search for "longer than 66 characters".
    26. Re:Uhhh by bjorniac · · Score: 0, Flamebait

      My undergrad (and I think this is the way with most UK institutions) graded:

      70+ First Class
      60+ Upper Second
      50+ Lower Second
      40+ Third
      30+ Pass
      29- Fail

      But then again, 10% of people got firsts, so I guess it's a little harder than the US (or we're stupider... nah)

    27. Re:Uhhh by Your.Master · · Score: 1

      Now that's grade compression.

      I'm used to:

      90%+ -- A+
      80% -- A
      70% -- B
      60% -- C
      50% -- D
      50% -- FAIL

      And sometimes people go with A-, B+, B-, etc. notations for things that are very near the cutoff to the next level.

      This of course has essentially nothing to do with the quality of the school, it's just an artifact of how marks are assigned. Acid3 would surely be a test at a school more like all the ones I've ever been to than your fabled ones (honestly, I always thought it was weird that we assigned a full 50% to failing marks and so only 50% could differentiate the vast majority of a class; that essentially 31-point scale seems obscenely narrow).

    28. Re:Uhhh by Bogtha · · Score: 1

      Going from there straight to "no columns" is pulling a fast one, though

      I didn't say anything about avoiding columns. I said they weren't a high priority.

      The only way of doing both 66 chars/line and packing the screen is by having several lines be adjacent; that is, by doing columns.

      You're neglecting to account for the fact that most websites aren't just paragraphs of text. They typically contain one or two sidebars, adverts, etc. The actual main content area of a website is usually significantly smaller. Even within the content area, horizontal whitespace is often necessary, for instance to indicate tree structures such as nested comments.

      Furthermore, you're forgetting that the CSS 1 & 2 specifications were written between 1996-98. Screen resolutions were a lot smaller then. Switch to 640x480 and tell me that it's difficult to fill the screen with 66 character wide lines.

      I'm toying with an idea for what I think I want: an option for a text block (p or div, no?)

      No. You're talking about layout. The element type used for the content is irrelevant to that.

      --
      Bogtha Bogtha Bogtha
    29. Re:Uhhh by Gothmolly · · Score: 1

      So that "best practices" and other ivory tower developer douchebags have something to point at and say 'nyah-nyah!'

      --
      I want to delete my account but Slashdot doesn't allow it.
    30. Re:Uhhh by DikSeaCup · · Score: 1

      Dude things have gotten easy for you people:

      90% or greater A (I think A+ was considered like 96 or greater IF pluses were used)
      80% - 89% B
      70% - 79% C
      60% - 69% D
      59% or lower F


      Honestly, it was that way for me pretty much through High School, and I was a Navy Brat - moved every three years usually, except High School was in four different schools (public Jr High in CA, public High in HI, parochial High in HI, parochial High in FL).

      Only in college (and in only in later classes) did I start hearing about this "curve" thing.

      Granted, I'm 37 now and the last time I attended a school was in 2004 for a Masters degree ...

    31. Re:Uhhh by Wildclaw · · Score: 1

      If higher percentage are needed for a grade, that is simply a sign of the tests being too easy.

      A good test should pose questions with a wide range of difficulty. Even using less than 50% for a failing grade like the grandparent said sounds too high. If someone is able to answer almost half the questions you can't really call that failing, unless the questions are way too easy in the first place.

    32. Re:Uhhh by pizzach · · Score: 1

      You can not tell me that rewriting your browser from scratch (Netscape 6) equals doing absolutely nothing with your web browser (IE 6) for 5 years.

      --
      Once you start despising the jerks, you become one.
    33. Re:Uhhh by DougWebb · · Score: 1

      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.

      That might explain why there isn't a layout style specifically for columns, but tell me this: why does CSS use this 'float' nonsense instead of the element layout models that have been used for GUI window layout for decades? It's trivial to define a GUI window in any language and IDE that has one element span across the top of the window, one across the bottom, and three packed horizontally in the middle. That's your classic "Header,Footer,Left Nav,Right Ad,Middle Content" web page layout, and we've known how to make that adjust nicely to variable window sizes forever.

      To get columns, the best approach would probably be a line-width style, which would let you specify that lines in an element should be 66em or whatever you'd like, and a columns style that lets you specify the min gutter width and max number of columns. (Min would be 1, and to maintain flexible layouts the browser should be able to adjust the number of columns between 1 and the max you specify, and also to increase the gutter width if the element is wider than needed to hold your max columns.)

      There; that took me all of 10 minutes to come up with a layout box model and multi-column style specification. Why is the W3C taking so long to figure out something useful?

    34. 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.

    35. Re:Uhhh by Blakey+Rat · · Score: 1

      Thank you, Doug, I agree entirely.

      I think part of my problem is people are taking the word "columns" to mean "free-flowing text columns" or something which I didn't really mean... I just meant columns, like having a nav column on the left side of page content like this website.

      In fact, come to think of it, when's the last time you saw a website that has zero columns? Virtually all of them have a navigation column or some other vertical division that implementing in CSS is a total hack. W3C totally missed the boat on this one, I think every rational person has to agree with that statement.

      The W3C still completely and totally fails to engage businesses to figure out what people are actually using the Internet *for*, and they're off on this ridiculous "make websites XML files" tangent without ever actually explaining the benefit of that approach. Their best idea in... well maybe ever is HTML 5, and that came out of left field.

      (Seriously, why do I, as a web developer, give a flying crap whether my page can be read by a XML parser or not? W3C should make an actual case for this before devoting years of time implementing it.)

    36. Re:Uhhh by Bogtha · · Score: 1

      why does CSS use this 'float' nonsense instead of the element layout models that have been used for GUI window layout for decades?

      Because CSS was designed for documents, not GUIs. The idea is to "pour" the document into the canvas, and make adjustments to the flow as necessary, not to divide up the viewport and put things into it. It makes some things quite a bit simpler and more efficient, especially when you remember that a major design goal of CSS was to incorporate the user's own styles.

      As it turns out, not many people were interested in the cascading part of Cascading Style Sheets, and the use of the web as an alternative application platform grew, so this approach doesn't look as sensible as it once did.

      It's trivial to define a GUI window in any language and IDE that has one element span across the top of the window, one across the bottom, and three packed horizontally in the middle. That's your classic "Header,Footer,Left Nav,Right Ad,Middle Content" web page layout, and we've known how to make that adjust nicely to variable window sizes forever.

      That's been trivial with CSS 2 for a decade using display: table. The only reason people turned to floats for things like that is because Internet Explorer doesn't support that part of CSS 2. Internet Explorer 8 will.

      There; that took me all of 10 minutes to come up with a layout box model and multi-column style specification.

      That's hardly a workable spec, it's more of an overview than a real specification.

      Why is the W3C taking so long to figure out something useful?

      It didn't occur to you to check the obvious place? Quote:

      This document has been a Working Draft in the CSS Working Group for several years. Multi-column layouts are traditionally used in print. On screen, multi-column layouts have been considered experimental, and implementation and use experience was deemed necessary in order to proceed. Several implementations have occurred over the past years, and this draft incorporates useful feedback from implementors as well as authors and users.

      In other words, they fielded ideas, people went off and tried them out, and kept finding problems or coming up with better ideas. It's exactly what would happen if you tried to get people to implement your "spec".

      --
      Bogtha Bogtha Bogtha
    37. 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.

    38. Re:Uhhh by yuna49 · · Score: 1

      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.

      Wow, that sounds great. Let me know when they release the native version for Linux, and I'll go try it out.

    39. Re:Uhhh by junglee_iitk · · Score: 1

      I read some replies you got and none of them were actually provide an answer - classic slashdot phenomena of beating the dead horse, which is nearest to your hand. (I should get a BadAnalogyGuy.v2 :) )

      Anyway, you are confusing goal with path.

      The tests are designed not to see which browsers are better at handling, but to provide higher bar of competition to all browsers. It is designed to provoke fanboyism among fans, and a sense of challenge among developers, but its aim is to promote compatibility by providing a common ground. For example, if all the browsers start getting 90%, you will know that they are compatible for at least 90% of all the tests (may be more, if they all fail on same tests, but at least 90%!).

      As you see, while the immediate response of a participant browser is to be a winner, the test is designed for the improvement of the loser. Which is IE in this case.

      And judging by Microsoft's response to Acid2, I am at least hopeful :)

    40. Re:Uhhh by doti · · Score: 1

      What happened to E?

      --
      factor 966971: 966971
    41. Re:Uhhh by yuna49 · · Score: 1

      I usually don't write endorsement comments, but your postings in this thread have been a model of clarity and forthrightness. I share your puzzlement with the apparent obliviousness of the standards-setting bodies to the actual design of web sites. Designing a standard language for communication among humans is a very different task than designing a protocol like TCP or a programming language like C. The W3C too often seems to think that web standards should mimic the latter.

      I understand some of the W3C's motivations; they're trying to build truly universal standards. While that's a noble goal, at the moment nearly all web content is read on screens through browsers. Ignoring that fact hinders the communication among humans that the invention of the World Wide Web so remarkably enabled.

    42. Re:Uhhh by Blakey+Rat · · Score: 1

      To the end-user, and industry at large, both are the exact same thing. Either way, we went years without a new Netscape/Mozilla and we went years without a new IE... it doesn't matter *why* the gap was there, but denying it's there because Mozilla "was working on it" is stupid.

      What did that time gain Mozilla, anyway? Firefox is, at best, neck-and-neck with IE7 (feature/performance-wise), despite being written from scratch.

    43. Re:Uhhh by Bogtha · · Score: 1

      And by taking their ball and going home, Netscape was handing Microsoft the monopoly in this area.

      I don't think continuing to develop their browser can truthfully be characterised as "taking their ball and going home", and I don't see what your point is. You tried to make out that Microsoft's and Netscape's actions were the same thing. I pointed out they weren't. Now you are attacking Netscape again. Why? What point are you trying to make? Or are you just looking for an excuse to bash Netscape? Your further complaints about them aren't relevant to what I said, which is that Microsoft's and Netscape's actions were very different.

      Of course the validater is going to scream and whine at you for using it

      Do you know what a validator is? No validator would "scream and whine at you" for using <font> if the DTD permits it, such as with a Transitional document type. The issue is not one of validity at all, but you sure seem to have a chip on your shoulder about validators. Once more, attacking something for apparently no reason. Why did you bring validators up?

      The machines can't be simplier, because they still have to render HTML 4 pages anyway.

      Circular logic. "Let's all use a complex document format because we all use a complex document format! Let's ignore planning for the future because the only thing that's important is what's happening right now!" Yes, with your attitude, we'll be stuck with HTML 4 for life. How inspiring.

      There's no reason to believe, especially in 2008, that XHTML strict will catch on to the point where browsers can ditch HTML rendering.

      Ditch? No. Factor out into legacy middleware to aid maintenance? Why not? And why are you judging the W3C's decisions in 1998 as if they had information available in 2008?

      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?

      Yes, why not? XML is far easier and simpler than SGML. For instance, try asking an average web developer when quoting an attribute value is necessary in HTML and when it is necessary in XHTML. They will get the XHTML right, but not the HTML. Try asking them to count the elements in <table><tr><td></td></tr></table> for both HTML and XHTML. They'll get XHTML right and HTML wrong. HTML is full of special cases. XML simplified it significantly.

      Are you familiar with how markup parsers work? It's not just the speed that matters. The complexity of the parsing code matters as well. Try comparing code to parse HTML with code to parse XHTML.

      If you don't like the FONT tag in HTML5, well, don't use it.

      That only helps producers of HTML 5. The people consuming it need to deal with that crap too.

      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

      Or maybe they did just that and found out that the importance of the fold is hugely exaggerated. Blasting the Myth of the Fold:

      Research debunking this myth is starting to pop up, and a great example of this is the report available on ClickTale.com3. In it, the researchers used their proprietary tracking software to measure the activity of 120,000 pages. Their r

      --
      Bogtha Bogtha Bogtha
    44. Re:Uhhh by Bogtha · · Score: 1

      I just meant columns, like having a nav column on the left side of page content like this website.

      W3C totally missed the boat on this one, I think every rational person has to agree with that statement.

      This is nonsense. The W3C gave you an easy way of doing exactly what you want a decade ago with CSS 2 tables.

      Seriously, why do I, as a web developer, give a flying crap whether my page can be read by a XML parser or not?

      Web standards aren't solely for the benefit of web developers, they are for the people implementing servers and clients as well.

      --
      Bogtha Bogtha Bogtha
    45. Re:Uhhh by Derek+Pomery · · Score: 1

      ACID3 is a target.
      It collects all the things that make a web developer go WTF, cuss, then find a workaround.

      It is good to have a target, it allows browsers to have something to aim at.
      Note that both WebKit and Mozilla have ACID3 tracking bugs:
      (Mozilla's spreadsheet below, not linking to bugzilla from /.)
      http://spreadsheets.google.com/pub?key=pNgBCwWdyRTT2JeiZn4B2Yw

      They are working towards it and will steadily improve, allowing for fewer WTF moments in the future.

      Note that IE8 brags about passing ACID2. And ACID1 did similar things for the box layout.

      These tests are a good thing.

      --
      -- perl -e'print pack"H*","6e656d6f406d38792e6f7267"' /. ate my old sig. Bastards.
    46. Re:Uhhh by pizzach · · Score: 1

      The late release gained the web and the industry as a whole a fairly standards compliant rendering engine. If Netscape/AOL had just released Netscape 5, the web would most likely still be dealing with Communicator 4's quirks like we deal with IE's now.

      Furthermore, the delay gained users a fairly flexible open source browser that will run on most hardware/OS configurations that will likely never again stagnate even if it did get a top market position.

      I for one am happy that the Netscape delay happened because we had gotten a much better product out of it and less browser confusion. I for one am disappointed the delay in IE because they did nothing, and planned nothing. All of the developers were just funneled to other projects until recently...and it shows...horribly at that.

      --
      Once you start despising the jerks, you become one.
    47. Re:Uhhh by Blakey+Rat · · Score: 1

      I don't think continuing to develop their browser can truthfully be characterised as "taking their ball and going home", and I don't see what your point is. You tried to make out that Microsoft's and Netscape's actions were the same thing. I pointed out they weren't.

      It doesn't matter whether or not they continued to develop it, the point is that neither company released anything browser-wise for several years. From my point of view, their actions were the same thing: no new browsers were released.

      Now you are attacking Netscape again. Why? What point are you trying to make? Or are you just looking for an excuse to bash Netscape? Your further complaints about them aren't relevant to what I said, which is that Microsoft's and Netscape's actions were very different.

      Yes they were. Microsoft built a fast and stable browser, while Netscape added so much crap to their browser that it could hardly run an hour without crashing, then sued when they lost marketshare.

      Is it a bad thing that IE7 was so long in coming? Yes, yes it was. But I don't give Netscape/Mozilla developers much credence when Netscape 6 was equally long in coming... it just makes them hypocrites.

      Circular logic. "Let's all use a complex document format because we all use a complex document format! Let's ignore planning for the future because the only thing that's important is what's happening right now!" Yes, with your attitude, we'll be stuck with HTML 4 for life. How inspiring.

      It's called realism. And pragmatism.

      Hell a lot of large, commercial Internet retailers have no doctype declaration at all in a jumbled mess of code. HTML 4 would be moving up for them.

      And that's not even considering all the thousands of archived sites... the content of the site might still be perfectly relevant, but you can no longer view it because your new shiny browser doesn't like the version of HTML it uses? That goes against everything the Internet stands for, as far as I'm concerned.

      Ditch? No. Factor out into legacy middleware to aid maintenance? Why not? And why are you judging the W3C's decisions in 1998 as if they had information available in 2008?

      Either way it has to ship with the browser, so I don't understand the difference between that and what I said.

      And, for the record, I think W3C's decisions were stupid by 1998 standards... they should know from the study of other Internet protocols that once something's out there on the Internet, it'll be out there until the end of time. Ignoring that fact, yes, that's stupid.

      Are you familiar with how markup parsers work? It's not just the speed that matters. The complexity of the parsing code matters as well. Try comparing code to parse HTML with code to parse XHTML.

      Ok, the browser can do it in .6 milliseconds instead of .8 milliseconds. Big whoop.

      The "complexity" of the parsing code is set via the lowest bar, like the site above. It doesn't matter how new and shiny XHTML 1 or 2 or 10 is, you'll still need to render that site, and you'll still need all the same code you have in Firefox and IE now to handle it.

      Now explain the benefit to me as a web developer or as an end-user. The W3C has never bothered to explain why I suddenly need to make my pages XML-- will you?

      That only helps producers of HTML 5. The people consuming it need to deal with that crap too.

      It's not consumed by people, it's consumed by computers. Computers can deal with that crap in a matter of milliseconds.

      Besides, if you can use HTML 4 to separate markup and style, you can use HTML 5 to as well. If you don't like tags like FONT, simply don't use them and everybody's happy.

      Now there's no denying that what is immediately visible is valuable screen real estate, but that doesn't change the fact that the width is virtually always the limiting factor in a design. Why do you think it's always

    48. Re:Uhhh by Blakey+Rat · · Score: 1

      I for one am happy that the Netscape delay happened because we had gotten a much better product out of it and less browser confusion. I for one am disappointed the delay in IE because they did nothing, and planned nothing. All of the developers were just funneled to other projects until recently...and it shows...horribly at that.

      How-so?

      IE has had three releases since Firefox has come out:
      1) The additional features that came with XP SP2 (not sure what version number this release is... 6.1?)
      2) IE 7
      3) IE 8 (in beta)

      Number one on the list is still pretty far behind Firefox's featureset, but added two of the most desired Firefox features: Flash blocking and more obvious secure site indicators. IE 7 has now added every feature that Firefox ships with, runs faster and uses less memory. I haven't tried IE 8 yet.

      It seems to me that IE 6, despite being ignored for several years, has caught up remarkably quickly.

    49. Re:Uhhh by DikSeaCup · · Score: 1

      I dunno ...

      I'd prefer that the engineer designing the stuff like cars or planes be able to answer a hell of a lot more than 50% of the questions on a test measuring his knowledge of the material relevant to his tasks ...

    50. Re:Uhhh by 3leggeddog · · Score: 1

      What good are airline schedules if few flights are on time?

      Well, at least they let us judge how bad "ontime performance" really is.

    51. Re:Uhhh by Bogtha · · Score: 1

      Your further complaints about them aren't relevant to what I said, which is that Microsoft's and Netscape's actions were very different.

      Yes they were.

      Well then we've come full circle, because the reason I originally responded to you is because you were claiming the opposite:

      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.

      The simple fact of the matter is that the reasons behind the delay in releases for both browsers were very different, and you acknowledge that, so can I take it you are conceding that it's reasonable to judge them differently for their actions?

      Either way it has to ship with the browser, so I don't understand the difference between that and what I said.

      Well firstly, no it doesn't have to ship with the browser. Ever heard of transcoding proxies? Some mobile platforms use them. Secondly, including a compatibility filter to statically translate legacy content is an entirely different ballgame to structuring the browser around the legacy content because nobody took the initiative to do any better. Just because there's legacy content out there, it doesn't mean it has to rule the world.

      they should know from the study of other Internet protocols that once something's out there on the Internet, it'll be out there until the end of time. Ignoring that fact, yes, that's stupid.

      Legacy formats and protocols die all the time. That's not stupid, that's a fact. Where's the demand for Gopher? Active channels? VRML? The bajillion file formats rendered by plugins during the 90s?

      Ok, the browser can do it in .6 milliseconds instead of .8 milliseconds. Big whoop.

      What part of "it's not just about speed" didn't you understand? Do you understand that code to parse tag soup is hell to develop and maintain compared with parsing XML? That developers have to actually spend time on this? Just because you are at the other end of the pipe sending this crap instead of receiving it, it doesn't mean the problem goes away.

      Now explain the benefit to me as a web developer or as an end-user.

      As a web developer, you have a simpler, more regular markup language to use. You gain all the advantages of the XML toolchain, so you can use XSLT to transform documents, embed data from other namespaces, etc. End-users only gain indirectly. The easier things are for developers, the quicker they get features, the less overhead is passed on to them in prices, etc.

      The W3C has never bothered to explain why I suddenly need to make my pages XML

      Of course the W3C have provided rationales. If you've missed them, you are blind. There's a summary at the top of the XHTML 1 recommendation. I find it very hard to believe you would honestly think that the W3C have never given rationales without deliberate effort to bury your head in the sand.

      And what's this about "suddenly"? The W3C have made a habit of providing upgrade paths and ways of dealing with legacy technology. When you characterise them as demanding immediate change, you are describing the opposite of their approach.

      It's not consumed by people, it's consumed by computers. Computers can deal with that crap in a matter of milliseconds.

      Computers need to have code written for them by people in order to consume it. It takes longer than milliseconds to write that code. Are you deliberately avoiding the point? I think I'm being pretty clear in pointing out that efficiency isn't the only fa

      --
      Bogtha Bogtha Bogtha
    52. Re:Uhhh by Blakey+Rat · · Score: 1

      Legacy formats and protocols die all the time. That's not stupid, that's a fact. Where's the demand for Gopher? Active channels? VRML? The bajillion file formats rendered by plugins during the 90s?

      I dunno, but I'd sure love to be able to view the images on this site: http://www.worldwar1.com/fracgal.htm

      That developers have to actually spend time on this? Just because you are at the other end of the pipe sending this crap instead of receiving it, it doesn't mean the problem goes away.

      Making 10 developers change their browser code is much easier than making 10,000 web developers change theirs.

      As a web developer, you have a simpler, more regular markup language to use.

      More regular, but not necessarily more usable.

      You gain all the advantages of the XML toolchain, so you can use XSLT to transform documents

      Why would I want to do that?

      embed data from other namespaces

      Why would I want to do that?

      etc.

      Yeah. So I can use XSLT to "transform documents" and I can embed data from other namespaces. And yet you haven't told me one actual benefit to it. You've just spouted buzzwords, can't you see that? Why would I even want to transform a document? Transform it into what, a car?

      I don't need new buzzwords, I already have enough of those thank you.

      Computers need to have code written for them by people in order to consume it. It takes longer than milliseconds to write that code. Are you deliberately avoiding the point?

      No, I just think it's a stupid and invalid argument. I missed the part where I'm supposed to change every web page I've ever maintained to XHTML to make someone else's job easier... why, again, am I doing this?

      Right, I get it. The W3C are at fault for not prioritising a need that you admit doesn't exist. Right.

      I didn't admit it didn't exist. There's no point to me replying to your untrue statement.

    53. Re:Uhhh by Bogtha · · Score: 1

      Making 10 developers change their browser code is much easier than making 10,000 web developers change theirs.

      If that were true, how do you explain the legions of web developers complaining about Internet Explorer's shortcomings? It's easier to get all the web developers in the world to change their code than it is to get one single browser vendor to change theirs.

      Regardless of whether it is easier in the short-term or not, it's whether it's a good idea that matters. You can muddle through life bolting a piece at a time onto legacy systems until they are twisted out of all recognition and are impossible to maintain, or you can realise that sometimes a careful refactoring can save you a lot of time and grief in the long run. If you've ever maintained a large codebase over a number of years, you'll know this is inarguable. If you always go with what is easiest at any given moment, you dig yourself a hole that can be very hard to get out of.

      More regular, but not necessarily more usable.

      It's more usable. Something being regular doesn't necessarily make it more usable, but in the case of HTML versus XHTML, that does happen to be the case. Do you disagree? I posted examples earlier.

      Yeah. So I can use XSLT to "transform documents" and I can embed data from other namespaces. And yet you haven't told me one actual benefit to it.

      I'm sorry, you have been representing yourself as knowledgeable about web development. I assumed you'd know the applications of these technologies. XSLT is a functional template language for XML. You feed it an XML document and a template, and it transforms it according to the rules laid out in the template. For instance, you could dynamically transcode XHTML to OpenDocument format or PDF. Embedding data from other namespaces is an extension mechanism. You can mix and match element types from different document formats. For example, you can embed mathematical formulæ into XHTML by using MathML or vector graphics into XHTML by using SVG.

      I missed the part where I'm supposed to change every web page I've ever maintained to XHTML to make someone else's job easier

      This part of the argument was talking about the inclusion of <font> in HTML 5. Have you written any code in HTML 5 that uses <font> ? No? Then you don't have any code to change.

      Right, I get it. The W3C are at fault for not prioritising a need that you admit doesn't exist. Right.

      I didn't admit it didn't exist. There's no point to me replying to your untrue statement.

      No, you didn't admit that. I showed that it was hugely exaggerated and you found a way to avoid admitting it by saying that it didn't matter whether it was true or not by making the ludicrous claim that mythical problems are as important as real problems. You know, I don't think you believe half the crap you are coming out with now, I think I've backed you into saying crazy shit because you can't admit when you are wrong.

      So let me rephrase. It is ridiculous that you are criticising the W3C for not placing a high priority on a layout technique that you haven't shown a need for. It is ridiculous that you think the W3C are idiots for solving actual problems rather than chasing phantom problems and pandering to myths. It is ridiculous that you claim that problems that don't actually exist should be considered as important as real problems.

      --
      Bogtha Bogtha Bogtha
    54. Re:Uhhh by DM9290 · · Score: 1

      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. uhhh... guess again.
      See: United States v. Microsoft, 87 F. Supp. 2d 30 (D.D.C. 2000)

      Microsoft was found to committed monopolization, attempted monopolization, and tying in violation of Sections 1 and 2 of the Sherman Act.

      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? Dell never got the choice, Microsoft made that choice for them. But Microsoft chose the slow bloated and unstable web-browser -- their own.

      --
      No one has a right to their *own* opinion. They have a right to the TRUTH.
    55. Re:Uhhh by Blakey+Rat · · Score: 1

      I'm sorry, you have been representing yourself as knowledgeable about web development. I assumed you'd know the applications of these technologies.

      I guess I'm just a total retard. But at least I'm not a total retard who's impressed with vapid buzzwords.

      XSLT is a functional template language for XML. You feed it an XML document and a template, and it transforms it according to the rules laid out in the template. For instance, you could dynamically transcode XHTML to OpenDocument format or PDF

      And why would I want to do that? You're supposed to be giving me *practical* examples. I could use a PDF print driver or copy-and-paste to do the same thing without the buzzwords. But, then again, if I wanted a PDF file, I probably wouldn't have been writing a web page in the first place.

      Embedding data from other namespaces is an extension mechanism. You can mix and match element types from different document formats. For example, you can embed mathematical formulæ into XHTML by using MathML or vector graphics into XHTML by using SVG.

      Except browsers don't support this, so what's the point?

      I'm not sold.

    56. Re:Uhhh by Blakey+Rat · · Score: 1

      Dell never got the choice, Microsoft made that choice for them. But Microsoft chose the slow bloated and unstable web-browser -- their own.

      Oh please... have you even *used* Netscape 3 or Netscape 4? Compared to IE 4 or IE 5?

      My point was that Netscape was lost anyway (yes I know Microsoft did illegal this and illegal that and we all hate them). Netscape couldn't produce a decent product to save their company, so they resorted to lawsuits instead.

    57. Re:Uhhh by Zumbs · · Score: 1

      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. While I do agree that IE uses much less memory and has a slightly better performance, it's not my experience that IE handles Javascript better. On the contrary, I've seen javascript seriously impair IE while FF handled it much faster.
      --
      The truth may be out there, but lies are inside your head
    58. Re:Uhhh by bjorniac · · Score: 1

      Flamebait? How is this "flamebait"?

    59. Re:Uhhh by craiglarry · · Score: 1

      most righteous statement all these talking heads have made so far: what's all the fuss about?

    60. Re:Uhhh by jonaskoelker · · Score: 1

      I didn't say anything about avoiding columns. I said they weren't a high priority. Okay, so how do you suggest I maximize the amount of text on the screen at any one time, while at the same time keeping lines fairly short?

      I could switch to 640x480, but that'd be a net loss: yeah, I'd get shorter lines, but I could get the same just by wrapping lines at 66 characters at my current resolution. That's be about as efficient (in terms of screen real estate use) as limiting pages to a single $n-pixel column: not efficient at all.

      Also, I think you're trying to argue against my suggestion for multi-column pages, but I don't see how your arguments work. Yes, there may be some instances (like you've pointed out) where my solution doesn't have a problem to solve. Great. What about the other instances, are there anything wrong with my idea for those?
    61. Re:Uhhh by Bogtha · · Score: 1

      Okay, so how do you suggest I maximize the amount of text on the screen at any one time, while at the same time keeping lines fairly short?

      Like the rest of my comment explained, most websites aren't just a single block of text. You don't normally have to make any special arrangement to keep lines short. Sidebars, adverts, etc. do that for you.

      I could switch to 640x480, but that'd be a net loss: yeah, I'd get shorter lines, but I could get the same just by wrapping lines at 66 characters at my current resolution.

      You completely missed my point. I was explaining one of the reasons why it was even less of a priority when the CSS specifications were being developed.

      I think you're trying to argue against my suggestion for multi-column pages

      No, I merely pointed out that you were going down the wrong path by thinking about it in terms of element types.

      Yes, there may be some instances (like you've pointed out) where my solution doesn't have a problem to solve. Great. What about the other instances

      For the second time, I don't have anything against columns. I'm merely pointing out that given the design constraints of the web, it wasn't idiotic for the W3C to not place a high priority on them.

      are there anything wrong with my idea for those?

      Well I don't like the fact in an n-column display, a reader would get to the end of the first column and be confronted with the start of the n+1 column. But I suppose you could get around that problem with heavy styling.

      Why bother coming up with your own ideas though? Do you have anything against the W3C's CSS columns specification? Why don't you post your ideas to www-style?

      --
      Bogtha Bogtha Bogtha
    62. Re:Uhhh by Bogtha · · Score: 1

      I guess I'm just a total retard. But at least I'm not a total retard who's impressed with vapid buzzwords.

      I gave you concrete examples of actual functionality and you know it. If you think that's "buzzwords", then you don't know the meaning of the word "buzzword". "Web 2.0" is a buzzword. Examples of how you can use XML are not buzzwords. But why am I bothering explaining? You know this, you just don't want to admit there's actual useful functionality that XML provides, so you are using nonsense "buzzword" arguments. You know you aren't making sense, I know you aren't making sense, so why bother keeping up the pretence?

      You're supposed to be giving me *practical* examples. I could use a PDF print driver or copy-and-paste to do the same thing without the buzzwords.

      I'm suggesting automatically providing web content as PDFs and you are suggesting print driver kludges and copy-and-paste as alternatives? I was right about you preferring to talk bollocks than admit you were wrong.

      Except browsers don't support this, so what's the point?

      You've totally lost track of the discussion now. We're talking about the justification for the W3C to develop XHTML in the first place. Browser support is irrelevant. In any case, you are wrong, there is browser support for MathML and SVG. It's not universal, but it certainly exists.

      --
      Bogtha Bogtha Bogtha
    63. Re:Uhhh by Blakey+Rat · · Score: 1

      I gave you concrete examples of actual functionality and you know it.

      No, I don't know it. It sounds pointless to me.

      I'm suggesting automatically providing web content as PDFs and you are suggesting print driver kludges and copy-and-paste as alternatives? I was right about you preferring to talk bollocks than admit you were wrong.

      Sure, why not? It's not like your XML PDF generator machine thing can run the Javascript on the page anyway, so what's wrong with just converting it to a PDF once and uploading it to the webserver alongside the page with a download link pointing to it? What's the difference between that and using XML?

      Of course, you're also missing the bigger point which is that if I wanted the data as a PDF, I probably wouldn't have put it on a webpage to start with... I would have put it in a PDF file to start with.

      I think that you've dived into these specs and recommendations so deep that you've actually lost the ability to think about things from the practical viewpoint. I see this in programmers all the time... my favorite example is the programmer who advertises that his application was built with a particular API, as if any customers give a flying crap. ("Built with Cocoa!" "Built with .Net 2!" Good for you, what do you want a cookie?)

      I ask for practical examples and I get a response consisting of nothing but acronyms starting with X. Buzzwords, whether you think so or not.

      Browser support is irrelevant. In any case, you are wrong, there is browser support for MathML and SVG. It's not universal, but it certainly exists.

      News to me. But, again, this might shock and dismay you, but I write websites in the real world. It doesn't matter how shiny the feature is, if no browsers support it, then it's a waste of my time. Here in the real world, people use real browsers, not some ethereal prototype browser W3C wants them to use.

    64. Re:Uhhh by Bogtha · · Score: 1

      It sounds pointless to me.

      Just because it's not useful to you, it doesn't make it a buzzword. People's requirements differ wildly. A buzzword remains a buzzword no matter who is involved.

      what's wrong with just converting it to a PDF once and uploading it to the webserver alongside the page with a download link pointing to it?

      Because we might be talking about a thousand pages of content administered through an online CMS. No, copy-and-paste and print driver kludges are not a universal approach.

      if I wanted the data as a PDF, I probably wouldn't have put it on a webpage to start with

      Yes, because nobody ever wanted content in two different formats before, did they?

      I think that you've dived into these specs and recommendations so deep that you've actually lost the ability to think about things from the practical viewpoint.

      And I think you are scrabbling around with kludges and excuses because you can't deal with the fact that XML can be useful.

      I ask for practical examples and I get a response consisting of nothing but acronyms starting with X. Buzzwords, whether you think so or not.

      That's simply a lie. I gave you descriptions of actual functionality. You then proceeded to tell me that you don't want to do those things and you can do them in other ways. Tough. It's still functionality, practical examples of things you can do.

      News to me. But, again, this might shock and dismay you, but I write websites in the real world.

      Ahh, yes, the "real world" argument. Loosely translated, it means "I haven't seen it, so it doesn't exist".

      I'm also a web developer, creating websites and web applications in the real world. You know how recently I was asked for existing web content, administered through a CMS, to be made available in PDF format? Last week. You know how recently I was working on something involving inline SVG? Last week. So all the work you can get is run-of-the-mill lowest-common denominator HTML crap. That doesn't mean there's nothing else out there.

      It doesn't matter how shiny the feature is, if no browsers support it, then it's a waste of my time.

      I've already pointed out that "no browsers support it" isn't true, yet you persist with this lie. If all you have to offer are more lies and excuses, don't bother replying.

      Here in the real world, people use real browsers, not some ethereal prototype browser W3C wants them to use.

      Real browsers like Firefox and Opera? Both of them have support for SVG and MathML.

      --
      Bogtha Bogtha Bogtha
  8. Which version of ACID test? by Anonymous Coward · · Score: 0

    The acid test website notes that the test may change over time as until it is debugged. Surely the page of collected results needs to record which version of the ACID3 test was used for each test, or at least the date on which each result was obtained?

  9. When you thought you could make ends meet... by f2x · · Score: 1

    Somebody moves the ends. IE 5 might just be passing it on a fluke. It's not as if it renders the Acid 2 smiley face better than 6 or 7. That said, either I'm not getting it, or the people setting up the acid tests aren't getting it- If no one is passing the "test" then the whole point of the test is moot. You might as well ask a politician for their detailed exit strategy in the war on terror. It's like granting a patent on something that never existed. It's what happens when you have standardized achievement tests in schools and teachers only teach to the test, while churning out students who lack critical thinking skills.

    It's looking less like the browsers aren't really failing so much as the goals keep shifting.

    --
    Blessed with all the brains that God gave a duck's ass, and twice the charisma.
    1. Re:When you thought you could make ends meet... by Anonymous Coward · · Score: 0

      Huh. Acid2 hasn't changed for years. They're still trying to figure out what they want to test with Acid3, and how to make an objective test for it. Yes, this means revising it.

      Also note, the Acid tests test standards compliance, in addition to error handling. Even if the "goals keep shifting", they're shifting towards the W3C CSS rendering spec, a perfectly objective document (and a correctly implemented browser would pass Acid2 and 3 by default).

    2. Re:When you thought you could make ends meet... by Anonymous Coward · · Score: 0

      Huh. Acid2 hasn't changed for years.

      Exactly my point. Those who write browser programs just begrudgingly made their application render the webpage correctly. As long as the broken CSS looked OK, then the browser was OK.

      They're still trying to figure out what they want to test with Acid3, and how to make an objective test for it. Yes, this means revising it.

      And that's what's wrong with it.

      Also note, the Acid tests test standards compliance, in addition to error handling. Even if the "goals keep shifting", they're shifting towards the W3C CSS rendering spec, a perfectly objective document (and a correctly implemented browser would pass Acid2 and 3 by default).

      And yet NO ONE passes acid 3! HELLO! NO ONE IS LISTENING TO W3C! They're just some crazy old man in the corner that keeps muttering about getting 40 rods to the hogshead!

      Things change.
    3. Re:When you thought you could make ends meet... by erlehmann · · Score: 1

      If no one is passing the "test" then the whole point of the test is moot.

      You are the one who doesn't get it. The point of the test is to expose rendering bugs in common, but incomplete implementations of web standards. The tests even fail validation to test if browsers deal with faulty code in the correct way.

      An ACID test is something like a common goal. While passing it does not proove that a spec has been fully implemented, it gives you a rough idea of how good a browser is regarding web standards.
  10. In other news by eggfoolr · · Score: 1

    Acid 3 fails the IE test getting a best score of 17%.

    Get with the program guys.... M$ discovered the Internet. It's theirs to stick their flag on wherever they like!

    (Bloody natives getting restless again)

    1. Re:In other news by flyingfsck · · Score: 1

      "M$ discovered the Internet"

      Al Gore worked for Microsoft?

      --
      Excuse me, but please get off my Pennisetum Clandestinum, eh!
  11. 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

  12. 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 calebt3 · · Score: 1

      Well isn't IE8 the first release in which MS actually slightly cares about W3C?

    2. 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.
    3. Re:Old Web Browser Standards by EEPROMS · · Score: 1

      Your last name would'nt happen be "Knight" and your first being "Black" ?

      More info can be found here and a short video here if you find reading a challenge so you can clearly understand why we are laughing at your comment

    4. Re:Old Web Browser Standards by Barny · · Score: 1

      Its due some time after Duke Nukem: Forever...

      Yeah, the joke had to be made, never let it be said I wouldn't sacrifice karma to ensure every bad pun is explored.

      --
      ...
      /me sighs
    5. Re:Old Web Browser Standards by Maestro485 · · Score: 1

      They must have changed something because I tried Konqueror 3.5.7 and it crashed, which is also what happened in the article.

  13. Re:And older firefox versions do better too by calebt3 · · Score: 1, Informative

    Firefox 3 beta 3 is worse. The nightly build (the one that theoretically most resembles the finished product at this point) is third in the rankings. Right behind two other nightly builds.

  14. 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

  15. They did something right... by Aegis+Runestone · · Score: 1

    In the days of 5.5:
    "Internet Explorer isn't crappy enough! We need to make it worse!"
    Thus, IE 6 and IE 7 were born.

    --
    -Aegis Runestone-
  16. 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.
  17. 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

  18. 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 audi100quattro · · Score: 1

      You mean Safari, WebKit and KHTML developers: http://webkit.org/blog/158/the-acid-3-test/

    6. Re:safari by Bogtha · · Score: 1

      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.

      Actually, Webkit is a fork of KHTML (Konqueror's rendering engine) and the two codebases have diverged quite a bit. If you read the Safari weblog post regarding Acid3, you'll see that Webkit was missing support for some CSS 3 selectors that Konqueror supported. The Konqueror developers provided patches, which is why Safari improved support here, not because it already supported it in an unreleased version.

      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.

      There's plenty there. If Internet Explorer didn't exist, the bugs and different levels of support between the other browsers would be perceived as being huge, but because there's such an obvious extreme outlier, it skews the perception of them.

      --
      Bogtha Bogtha Bogtha
    7. Re:safari by Brett+Buck · · Score: 1

      >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.

            Exactly! That's a basic fallacy of the test (or, more accurately, the interpretation that people are making of passing or failing the test). It's not intended to be comprehensive, so you can go in, run the test, see what fails, and just fix what it necessary to pass - not necessarily prove that your browser is 100% compliant.

                Brett

    8. 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
    9. Re:safari by makomk · · Score: 1

      It's more accurate to say that WebKit is mostly open source. Apparently, it uses closed-source binary blobs based around private APIs and OS internals for various functionality under Mac OS X. (This used to include such vital things as font rendering.) Personally, I think this is probably a violation of the LGPL - it only allows you to use the library from closed-source code, and modifying the library so that it's dependent on closed-source code (other than the OS libraries) is still forbidden.

    10. Re:safari by bunratty · · Score: 1

      WebKit is forked from KHTML, so are any fixes to KHTML being ported to WebKit? Even if so, I don't think KHTML developers are contributing much to Safari doing better on Acid3 recently. And aren't the developers who do most of the work on WebKit mostly Safari developers working for Apple, just like the developers who do most of the work on Gecko are mostly Firefox developers working for Mozilla? It seems like it's Safari developers contributing the most to development builds of Safari doing better on Acid3, just the same way it's Firefox developers contributing the most to development builds of Firefox doing better on Acid3.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    11. Re:safari by Wildclaw · · Score: 1

      What this does seem to indicate however is that the Safari developer team is far better at bug fixing for what ever reason. Maybe they have better prodedures in place. Maybe their source code is better structured, making it easier to find a fix bugs. Maybe they have fewer bugs as a whole so they can focus more on the ACID test.

      Of course, it could also just be a marketing move.

    12. Re:safari by Anonymous Coward · · Score: 0

      To be fair if you're passing acid2 and acid3 you've got all the "important" ones down *and* most of the unimportant ones. If the acid tests weren't mangled messes of broken CSS by design, firefox, opera, and safari would all pass... the point of the acid tests is that they can't stop there, the goal is to get them to the point where they all render CSS exactly the same way - even if it's a mangled, broken mess. That's why the CSS standards detail what to do in the case of invalid code.

    13. Re:safari by Anonymous Coward · · Score: 0

      Try reading the link, which is redundant in this thread.

      "Support for CSS3 Selectors
      We added support for all of the remaining CSS3 selectors. These include selectors like nth-child, nth-of-type, last-child, last-of-type, etc. These selectors were already implemented in KHTML, and the KHTML developers had even kindly provided patches for us in the relevant WebKit bugs. Therefore it was a simple matter of taking those patches, updating them to the WebKit codebase, and then merging them in. A big thanks to the KHTML developers for their hard work in this area."

      These patches are pretty old too, Ars mentioned them in an article more than 6 months old: http://arstechnica.com/journals/linux.ars/2007/07/23/the-unforking-of-kdes-khtml-and-webkit.

    14. Re:safari by bunratty · · Score: 1

      Try reading the Acid3 test description, which is entirely relevant to this thread. It does not appear that Acid3 tests CSS3 selectors. I don't think that KHTML developers are contributing much to Safari doing well on Acid3. It's mostly Safari developers.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    15. Re:safari by 99BottlesOfBeerInMyF · · Score: 1

      Actually, Webkit is a fork of KHTML (Konqueror's rendering engine) and the two codebases have diverged quite a bit.

      Haven't they merged back together yet? I know the Konqueror team announced the decision to pull their CSS 3 stuff into Webkit and switch over, many months ago.

      ...you'll see that Webkit was missing support for some CSS 3 selectors that Konqueror supported.

      That was the main item missing from the Webkit fork, but does anyone know if those were tests in Acid3? It seems likely.

      you'll see that Webkit was missing support for some CSS 3 selectors that Konqueror supported.

      Maybe so, but I generally don't need anything too fancy and even for things that are rarely ever used because IE does not support them (like XHTML) I don't have any real problems with any of the major browsers. For more advanced uses, I could see it being an issue, but I'm not sure how common those uses are (or would be).

    16. Re:safari by Anonymous Coward · · Score: 0

      Haven't they merged back together yet? I know the Konqueror team announced the decision to pull their CSS 3 stuff into Webkit and switch over, many months ago.

      Yes, they have. KDE 4's Konqueror uses Webkit.

    17. Re:safari by poopdeville · · Score: 1

      WebKit is forked from KHTML, so are any fixes to KHTML being ported to WebKit?

      Get with the times. KDE dropped KHTML in favor of Webkit.

      --
      After all, I am strangely colored.
    18. Re:safari by audi100quattro · · Score: 1

      Not yet, the Konqueror shipped with 4.0.2 is the highest rated browser on the list that isn't a nightly or beta build, and it's still using KHTML. Work on bringing KDE interfaces to WebKit hasn't shown up yet anywhere I know of. Maybe by 4.1.

    19. Re:safari by poopdeville · · Score: 1

      Okay, you specifically said you weren't counting nightlies. Fair enough.

      Still, nightlies are where it's at. Especially since KDE 4 is basically a developer preview anyway. KDE's nightlies are more usable and stable.

      --
      After all, I am strangely colored.
  19. 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.

  20. Simple answers for simple questions by Pr0xY · · Score: 1

    the answer is simple, the value given does not directly equate to a percentage of conformance, it just means it screwed up earlier or later...but does not indicate how much it screwed up by (or more importantly what ELSE would screw up). So i would imagine that IE 5.5 probably has does some things simply "differently" from the later versions that make it fail at a different time, but that doesn't mean it failed less badly.

    proxy

    1. 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.
    2. Re:Simple answers for simple questions by pembo13 · · Score: 1

      These are an independent collection of tests.

      --
      "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
    3. Re:Simple answers for simple questions by yuna49 · · Score: 1

      It would be nice if they had enabled a scrollbar in that popup so I could read the whole list (Firefox 2.0.0.12/Linux 2.6).

    4. Re:Simple answers for simple questions by ais523 · · Score: 1

      They did. Try holding down shift when clicking on the A; the entire page will be replaced with the list in the popup, so you can use your browser's scrollbar to scroll through the list, and/or copy/paste the list elsewhere.

      --
      (1)DOCOMEFROM!2~.2'~#1WHILE:1<-"'?.1$.2'~'"':1/.1$.2'~#0"$#65535'"$"'"'&.1$.2'~'#0$#65535'"$#0'~#32767$#1"
  21. 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.
    2. Re:Maybe this is obvious but... by aug24 · · Score: 1

      You don't, and this is even commented on at the test: there may be bugs, and this test may change as a result.

      Justin.

      --
      You're only jealous cos the little penguins are talking to me.
    3. Re:Maybe this is obvious but... by Anonymous Coward · · Score: 0

      Except that you do, by inductively following the rules.

  22. IE5 by rubah · · Score: 1

    I wonder why they didn't test IE5mac :]

  23. 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.

  24. Re:So if I understand you correct.. by mike_sucks · · Score: 1

    Nah, I just to sound like one. :)

    --
    -- "So, what's the deal with Auntie Gerschwitz et all?"
  25. No chidrenz lef behinded by Anonymous Coward · · Score: 0

    59% or lower = A
    0% = B = PASS

  26. 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

  27. Still not enough old browsers! by Tycho · · Score: 0

    I think that more systems should be tested. Try IE 5.5 on a copy of WinME, if someone tries this, IE might crash, several times. Or perhaps IE 5.5 on MacOS 9 and MacOS X? The Newton MP 2000 has a web browser too. Then there are all those old versions of Netscape Navigator stretching back to 1994. What about lynx, how well does it render Acid3?

    --
    Impersonating Tycho from Penny Arcade since before there was a PA.
    1. Re:Still not enough old browsers! by neunon · · Score: 1

      Two things: 1) The browser needs Javascript for it to work. (I did try IE 5.0, 4.01, 3.0, but none of them even came close) 2) Your name is awesome.

  28. Standard too hard to meet by Anonymous Coward · · Score: 0
    I don't understand why we need a web standard which is so complex that no browser can comply with it.

    Okay, ACID is designed to find browser bugs. But I think my point remains valid; if the web standards had been a bit better designed (or perhaps merely a bit simpler), then the bugs would be less numerous and it would be easier to write a compliant HTML document.

  29. 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.

  30. regressing by agendi · · Score: 1

    The world has gotten so used to expecting so little from the internet (and MS browsers in particular) that the standards are regressing to match. The alternative is too horrible to contemplate (that ie 5.5 was ahead of it's time).

    --
    I just can't be bothered.
  31. Re:So if I understand you correct.. by quonsar · · Score: 1

    re: your sig that would be "et al"

  32. Re:You shouldn't be supporting standards by Secret+Rabbit · · Score: 1

    If you need to worry about "your 12 year-old self competing with" you, then I would say that you need to revisit your product rather than the *perceived* effort going into it.

  33. Re:You shouldn't be supporting standards by bandersnatch · · Score: 1

    So non-standards compliance browsers are now "high quality"? and we should all be creating more "high quality" crap and so the gravy train never ends? Competition will bite you in the ass sooner or later, just ask Detroit or RIAA.

    In the meanwhile, why don't you enjoy some music and chill? What' that? Oh sorry, that non-standards compliant DRM'd CD doesn't play on your PC/Player/etc. I'll sell you one. It's a bit pricey at $200000, but it's "high quality" and my employees will that you for it.

    Ultimately, it's the customer that pays the bills. You may be able to make a temporary living off of inefficiency by providing less at a higher cost, but I wouldn't make it my business model. The market adjustment is a bitch.

  34. 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>
  35. Re:You shouldn't be supporting standards by Bogtha · · Score: 1

    But if it's complex and frustrating to do, then I don't have to worry about my 12 year-old self competing with me.

    If the ability to handle browser incompatibilities is the only thing that separates you from a twelve year-old, you probably don't deserve your job or its above-average pay scale. Competent developers don't fear competition from children.

    --
    Bogtha Bogtha Bogtha
  36. Re:You shouldn't be supporting standards by thpr · · Score: 1
    I vote for standards.

    Standards are definitely better for consumers. But many of you seem to forget that you aren't just consumers -- you're employees too.

    ...employees of companies that are dependent on technology getting cheaper. ...and employees of companies whose consumers are dependent on technology getting cheaper. You seem to think that the technology world controls the economy. In fact, it's not the largest part of the economy. Technology doesn't have that control, and it never will, for numerous reasons.

    Making technology more complicated and more expensive is not beneficial for consumers of what you sell. Businesses measure the ROI of projects. If you drive up the cost, you drive down the ROI. Eventually you will encounter a situation where no projects will be implemented. Yes, that may take a few years, but it will happen. Then, you will have killed your entire company, which I think is much worse than fighting to maintain your standard of living.

    Today, third-world cheap labour for metal and plastic and paper trumps any local labour. Do you want tech jobs to go the same way?

    And you believe that by fighting against standards you can stop it?

    It also seems that you want to effectively form a cartel. I have news for you: The people in India don't want you to form a cartel. They want standards, because it allows the job transfer. It will raise their standard of living. Thus, they will create and follow standards even if you do not. If you believe that the large companies that are consumers and not developers of technology will stay with a more expensive solution because you hope beyond hope that they will pay you extra... then you're dreaming. The bad news for you in that picture is that the companies that purchase web development services will transfer and outsource that work. Again, by trying to stop progress, you doom your own company.

    There are many other reasons your logic fails to be reasonable: Economic production location is based on relative efficiency rather than absolute efficiency, not all of the resources/services you provide need to be scarce to be valuable, complexity and frustration does not translate into value, supporting your clients doesn't mean giving them inferior products at higher cost, etc.

    The answer to good wages is not to hope progress stops. The key is keeping a high skill set, being flexible, and ensuring that you are paying attention to what technologies and products are becoming commodities. As an employee (and not self-employed), means, of course, a touch of luck is involved as well. The answer is not to fight standards.

  37. Re:You shouldn't be supporting standards by Viceroy+Potatohead · · Score: 1
    I'm not entirely sure you're not joking, but I'll respond as if you aren't...

    What an asinine POV.

    I run an internet application programming business. I don't want standards. Browser standards will make it really easy for anyone to create a web-page semi-well. Right now, my efforts are spent on the high-tech skills of managing a high-tech industry. If things become too easy, my skills will switch to competitive sales. That's good for the consumer who doesn't care about excess quality, sure. But it's just plain aweful for my employees. I'll pay them less, I'll outsource more. If I were your boss, I'd fire you. If I were your employee, I'd quit. Someone who is more interested in maintaining their corporate/company's status quo, regardless of the market, is useless. I'm sure the flailers would have loved to artificially inflate their value compared to the threshing machines, or the farriers to do the same with the automobile. In reality, someone will undercut you. There is more profit in undercutting you than in your protectionism. Your view has nothing to do with capitalism, but protectionism. You want your market to remain esoteric enough to avoid competition. As you said "it's not hard to program". You're doing yourself and your employees a disservice by relying on obfuscation/secrecy instead of quality to sell your product. You might get lucky for a while due to inertia of the system (perhaps even your whole life), but you can only be successful in a capitalistic environment two ways (AFAICT): Stack the deck(eg influence legislation), or build a good hand(eg build a better mousetrap). Since you've mentioned competing against 12 year olds, I'll assume that you aren't in a position to stack the deck, and you explicitly stated that quality wasn't your goal (see your comment about consumers), so I assume your entire strategy is making sure you hide your cards well enough that no one even knows if you're playing the game.

    This is a nice touch:

    I'll produce high-quality products and services, I'll stand behind them, and I won't worry about competition. You've already said the exact opposite. In fact, the gist of your post was the exact opposite. You're supremely worried about competition, to the point where you don't want either market stability, market information, or standardization to wreck your money-grab.
  38. 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 HeroreV · · Score: 1

      Even if unintentional, it isn't something that was introduced by the mirrors. That's all I was trying to say.

    3. 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
    4. Re:mirrors not introduce change by HeroreV · · Score: 1

      ... one of the mirrors happens to be webstandards.org ... Hold up. You're srsly claiming webstandards.org is a mirror? Well then we must not be using the same definition, because that sure don't sound like a mirror to me.
    5. Re:mirrors not introduce change by Bogtha · · Score: 1

      Yes. Just because you can easily guess that it's actually the same site served in two different ways, it doesn't mean it looks that way to a web browser. So far as HTTP is concerned, webstandards.org and www.webstandards.org are entirely different sites. The best practice method of making one site available through two hostnames is to have one canonical hostname and set the other to perform a redirect. Often this is overlooked, leading to problems like lower cache hit ratios, cross domain issues and various other annoyances. It's a mirror — an inadvertent and purposeless mirror, yes, but a mirror nonetheless.

      --
      Bogtha Bogtha Bogtha
  39. Re:You shouldn't be supporting standards by pembo13 · · Score: 1

    That is the most selfish post I have seen for the entire year.

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  40. Typical by oil · · Score: 1

    Typical Microsoft, they embraced when they should have extended.

  41. Re:You shouldn't be supporting standards by Penguinisto · · Score: 1
    Err, as a former Electronics monkey, I have but one thing to say: Up your skillset, buddy.

    Electronics? It once went from being a big mysterious thing that professionals were needed to maintain, to being a commodity item. Where once you needed a pro to trace a problem to a discrete component (IC, resistor, capacitor, etc), now any half-educated tech can trace it to a malfunctioning board, replace it, and all works well again. Consequently, electronics techs were replaced by generic maintenance techs.

    If you think for one second that the world owes you a living because you know how to throw together HTML, CSS, and half a dozen other scripting languages into a website that looks pretty? Err, sorry, but no. It don't work that way.

    I went from electronics to computers to systems administration, and am now flirting with programming and engineering as part of my duties.

    If I sat there then (like you're doing now) and whined about the impending commoditization of a tech that I make money off of? I'd be living in a trailer park somewhere on Welfare, bitching about how life is soooooo unfair. Instead, I'm working for a Fortune 100 corp for a healthy salary and quite a decent life, with a hard-won lust for challenge and a constant eye on emerging technologies.

    The secret is simple: instead of worrying so much about how your cash cow is swirling the drain, work on how to provide the best value now, and where to take you and your employees in the future.

    /P

    --
    Quo usque tandem abutere, Nimbus, patientia nostra?
  42. 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.
    1. Re:Some insight regarding the Acid 3 Test by muszek · · Score: 1

      Yeah, the point is that we're wasting thousands of hours of work because IE almost gets those points.

      I think I can safely assume I speak for everyone who has anything to do with web design when I say I have a really hard time refraining from swearing like a sailor when I speak about IE.

  43. For completeness... by OwenMarshall · · Score: 1

    You missed Daniel Glazman, who contributes code for Mozilla.

    Apologies for my pedantry.

  44. Put another way. . . by Fantastic+Lad · · Score: 1

    There was a time before computers that companies employed hundreds of women punching data into manual adding machines in warehouse-like accounting departments.

    Then a host of clever people decided that technology should be explored and refined, and the result was a new type of electronic universal adding machine which eventually caused all of those jobs to dissolve. --It also eventually resulted in the internet and the creation of your current job.

    So we could either live in a world afraid of change which has no computers at all and a lot of 'safe' wage-slaves doing millions of hours of monkey work, or we could live in a world where exploration and refinement drive the human experience. . .

    -FL

    1. Re:Put another way. . . by holophrastic · · Score: 1

      I agree with all of what you've said. At this point, in 2008, with my business the way it is, I vote that we stay here for now. I'll kindly re-cast my vote when I die -- I'll put it into my will tomorrow.

  45. Why? by laparel · · Score: 1

    I don't think Microsoft deliberately wanted to break the standards. What would they get? They aren't becoming the standard that you claim so, they are just allowing other browsers to take more bites out of their market share. Now I know /. hates MS and would like to think that they're evil, maybe so... but in the IE compatibility-development department I think they've just become incompetent and complacent due to their monopoly.

  46. Re:And older firefox versions do better too by JebusIsLord · · Score: 1

    I think its really interesting that safari HEAD is at the top, while the most recent release (only a few months old) is towards the bottom. Safari was the first to meet acid2, and my guess is they are focusing on Acid3 now. Any browsers that came out before the Acid3 test was released are doing absolutely dismally.

    I don't think these numbers mean much just yet... Lets check again in a year to see how they've progressed. Hopefully the IE8 team consider this a priority.

    --
    Jeremy
  47. 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.

  48. Why use IE?! by rice_burners_suck · · Score: 0, Troll

    I don't know why people still use IE. There's Firefox, there's Opera, and on both Mac and Windows, there is Safari too. There are plenty of other browsers out there if these three aren't good enough for you. Why in the world would anyone use IE?!?!? This is a sincere question. Would someone please tell me?

    1. 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...

  49. Re:And older firefox versions do better too by Anonymous Coward · · Score: 1, Funny

    I don't think these numbers mean much just yet... Lets check again in a year to see how they've progressed. Hopefully the IE8 team consider this a priority. Who cares? Really ...
  50. Re:You shouldn't be supporting standards by lantastik · · Score: 1

    Stick a fork in you, you're already done.

    Your attitude is just like that of a guy we fired not too long ago. He went through with a little script and deleted all the comments out of his code that he never bothered to check in to source control. It was his thought that we would come crawling back to him because we couldn't maintain his crappy spaghetti code. It was okay though, we threw an intern at it and all was well in under a week.

    If you are worried about monkeys (or kids for that matter) taking over, you've already lost. Now...where is my t-shirt about replacing you with a shell script?

  51. The explanation is simple by 2ms · · Score: 1

    IE 5 and IE 5.5 where developed during the period during which it appeared the government was going to atually do something about their monopoly -- during the period when DOJ was building their case and everyone was getting ready for what should have been a huge trial.

    Everyone in their right mind (presumably including MS) was expecting something big like a breakup of the company was going to happen. So MS was having to play by the rules there briefly rather than the usually sabotaging anything they didn't already have monopoly control of. Once the trial was over, MS go back to trying to block out competitors by including IE as default browser on every PC sold and making it deliberately incompatible with standards so all sites would have to develop for compatibility with IE, thus being incompatible with anything else.

  52. Re:And older firefox versions do better too by Niznaika · · Score: 0

    Very strange that if AdBlock is active Ff 3.0b5pre scores 68 not 69 as it does without it.

  53. Just in: by uvajed_ekil · · Score: 1

    Windows 3.11 For Workgroups beats Vista at many tasks, and will run reasonably well on a 486. Is this a trend for Microsoft, older software outperforming newer software?

    --
    This is a hacked account, for which the owner can not be held responsible.
  54. Re:Well unfortunately... by RuBLed · · Score: 1

    lols, how could i be redundant and overrated at the same time considering that I'm one of the early posters and there is no in soviet russia jokes yet.. ohh I get it.. in soviet russia... hmmmm

  55. COMPLIANCE NOT PERFORMANCE by v(*_*)vvvv · · Score: 1

    This test is for compliance with w3c. It has to do with accuracies, not speed or user experience.

    The truth of the matter is, IE is its own standard because every developer must comply with it, as is Mozilla. And from the user's standpoint, this test again means nothing because it has nothing to do with experience.

    Finally, to say IE5 beats IE7 is another distortion of substance, as they are actually 14%, 13% and 12% in their results, which, if isn't within the margin of error, is within any margin of approximation - they are all the same. The difference in the score between first and second place is 16.

    These curve ball articles really do a disservice, as they are only interesting when distorted. If the boring truth were the headline it would read "IE continues to ignore W3C as everyone and their mother continue to follow its specs".

  56. I have no idea if they are still doing it, by Britz · · Score: 1

    but it used to be that they implemented the stuff in their own browser: Amaya

  57. my OLPC XO laptop scores 58/100 by dominux · · Score: 1

    I am running Sugar build update.1 691 The browser is based on Gecko

  58. 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.

  59. Re:Because by phagstrom · · Score: 0, Offtopic

    Nope - IE does not need at crack to work. Not even a NOCD patch... ;-)

  60. Many real world pages are tuned for IE only by gelfling · · Score: 1

    That's why I keep IE Tab installed on FF. So the standard is probably meaningless to the wider population of sites.

  61. tweaked to pass the test? by v1 · · Score: 1

    I suppose this raises the basic question of just how meaningful a public test like this is if everyone is actively working on their project for the specific purpose of passing the test. That's not a whole lot better than the allegations we saw earlier of browsers whose rendering engines tried to detect test pages and adjust their rendering in an attempt to pass it. I give kudos to the safari team for getting that far into the test, but I question just how meaningful that is when you consider it didn't pass that far because of how well it was designed - it got that far because it was specifically worked on to get that far on that specific test.

    The true measure of a browser's test is of course how well it does on the day the test is released, which as a previous post points out, smoked most browsers pretty bad.

    --
    I work for the Department of Redundancy Department.
    1. Re:tweaked to pass the test? by v1 · · Score: 1

      I would like to amend my comment though - the speed at which they take a browser that fails a test badly, and bring it up near full pass, and then the time it takes to actually pass the test, should be a much more respectable measure of the browser. Not of it's quality per se, but as a demonstration of the commitment and responsiveness that the development team has to making it work better.

      Ideally the browser should do very well on the day the test is released, AND pass the test within a week.

      --
      I work for the Department of Redundancy Department.
  62. But MSIE 5.5 still beaten by Lynx... by hotfireball · · Score: 1

    Subj. ;-)

  63. Standards vs. usage by MisterSquid · · Score: 1

    Your logic proves the point of the need for standards which are not suggestions, as you construe them, but recommendations. The point of standards is not to document the state of the art but to provide a common reference point for everyone to use.

    Following your logic, "standards" is synonymous with "observed behavior" which would mean that the behavior of the most-used rendering protocol would be the "standard." Can you see the problem? That would mean some flavor of IE would be the standard by the fact of being the most prevalent.

    Standards don't describe the vernacular. Standards establish guidelines.

    --
    blog
  64. Features? by walterbyrd · · Score: 1

    By "features" you mean the ability to render sites that are specifically built to not work with anything but the latest version of msie? Such as msft's own site?

  65. Re:Very simple - it's EEE by walterbyrd · · Score: 1

    > > 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.

    WTF? Are you aware of msft's history? Controlling the standard is central to msft's business model. Msft's philosophy is: "control the standard and the money will follow." Msft's EEE strategy has been well established - and not just on slashdot. Once msft get's of control of the standard - which msft did by msie 5.5 - msft then goes to work on extending the standard.

    > Back when Internet Explorer 6 was being developed, they were in direct competition with Netscape.

    I think you may need to review your timeline. By the time msie came out, msft owned over 80% of the browser market:

    "5.x versions attained over 80% market share by the release of IE6 in August 2001."

    http://en.wikipedia.org/wiki/Internet_Explorer_5

    > And when Internet Explorer development was restarted, they were responding to a call for improved standards support,which they have delivered on.

    Ah yes, the incompatibilty "features" were put in because of user demand, just like DRM, and WGA. Isn't that standard msft PR?

    > I'm sorry, but deliberate sabotage is a ridiculous way of explaining this.

    Just like it's ridiculous to think that silverfish, or OOXML, are supposed to lock people in to msft's proprietary standards, right? Why will msft's own website not work with msie 5.5? And as I understand it, msft is going to incorporate silverfish into their own site.

  66. IE8 may not be that great - article by walterbyrd · · Score: 1

    "There are quite a few good things about the Microsoft release, such as showing that HTML5 is looked at, Acid2 is (almost) being passed, and CSS support is improving, but there are quite a few evil things as well"

    http://annevankesteren.nl/2008/03/ie8-bad

  67. Re:And older firefox versions do better too by Big_Mamma · · Score: 1

    Webkit nightly (r30881) with Safari 3 on Windows XP = 90%, same as OS X. Too bad the text rendering is kinda broken, the anti-aliasing looks horrible, or it could become one of the major players on this platform.

  68. Re:So if I understand you correct.. by mike_sucks · · Score: 1

    True, except it's a quote. I'd put a [sic] in there but you know, why change now?

    --
    -- "So, what's the deal with Auntie Gerschwitz et all?"
  69. Re:Mod parent down; incorrect information by calebt3 · · Score: 1

    It was accurate as far as the table was concerned whet I posted.

  70. Re:And older firefox versions do better too by Bert64 · · Score: 1

    Not really...
    Adblock intentionally ignores elements of a page, by running adblock you are not seeing the site as it's coded. Acid3 is all about your browser displaying what the code tells it.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  71. Re:And older firefox versions do better too by JebusIsLord · · Score: 1

    Who cares? Web developers are the first ones who come to mind. The second is myself and anyone else who uses IE at work (which is most of us, last time Slashdot checked MOST visiters were still using IE!)

    --
    Jeremy
  72. Re:And older firefox versions do better too by JebusIsLord · · Score: 1

    Yeah, I know. Out of curiosity, why did you get +5 insightful just for just hammering home my point?

    --
    Jeremy
  73. Government procurement should REQUIRE compliance.. by dpbsmith · · Score: 1

    The era of real competition in mainframe hardware did not begin until the U. S. Government started requiring a COBOL compiler, capable of passing a validation suite, as a condition for government purchase of computers.

    On a much smaller scale, the era of real competition in the MUMPS language did not begin until the VA started requiring a MUMPS system, capable of passing a validation suite, as a condition for government of computers.

    The U. S. Government should require, as a condition for purchasing computers, that the default browser on the supplied OS be standards-compliant... e.g. should achieve a specified score, such as, say, 100%, on the ACID3 test.

    When it procures things, the government is part of the free market. And it is one of the few entities powerful enough to engage with Microsoft in a real negotiation between equals. The National Institute of Standards and Technology has the technical expertise to know what standards are, and what compliance is, and how to test it.

    Just as with tanker aircraft, the government should buy what best serves the government's needs, without regard to what best serves the needs of The Boeing Company, or Microsoft Corporation.

  74. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    See, you've missed my point when you've said "ultimately, it's the customer that pays the bills".

    My point was that it's not the customer that pays the bills, it's the customer's employer that pays the bills. That is my point.

    Because that $200'000 cd player was made here in Canada/U.S.. But your $25 player that you have now, came from Taiwan. So you've given $25 of your economy's worth away to another country, another culture, and to other people. You've exported cash. You've eliminated jobs.

    Now I'm not asking for our countries to become self-sufficient. Certainly we should import the things that we don't have, but we have humans, and we shouldn't be exporting work when we have unemployed and debts or deficits.

  75. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    The reason we don't fear competition from children is because we have two things that those children don't have. We have experience, and we have existing resources.

    Existing resources amount to servers and people and such already in place. That's money. Any child/start-up with money can get that stuff fairly quickly - i.e. a few months.

    Now our experience is the only thing to practically distinguish us. If you make that experience common-knowledge, and you remove the necessity for half of it, then that child/start-up has no trouble competing with us because they can do so on price.

    You're forgetting, I used to be that child/start-up and yes, I took customers away from larger companies like I am now. Yes I lose current projects to smaller shops willing to do little with less. And now I'm starting to compete with ibm's business solutions in much the same way.

    If you make it easy to do, there will be more people doing it. That's just plain logical. Browser incompatibilities are simply one of many such things. But it's still a significant factor -- and it's the one that's most easily explained to potential clients: if you go with that smaller guy, or your nephew, it'll be fine but it won't work on every browser. That's an easy explanation. It's easier than cross-integrated functionality, and it's easier than explaining the concept of down-the-road and scalability. On the other hand, the little guy has the easiest of all explanations -- it's cheaper.

  76. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    Ah, but if you mold C into perl, php, java, and ruby, then it does make programming easy. Then you can have tonnes of programmers cranking out software that works, and is perfectly decent, and gets programmed faster. Now as a C programmer, you'll have to explain why a project should be done in C and not in, say, VB. I'll bet that every advantage of C over VB is incredibly difficult to sell to just about any non-technical small business.

  77. 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.

  78. Re:You shouldn't be supporting standards by Anonymous Coward · · Score: 0

    Ah, but if you mold C into perl, php, java, and ruby, then it does make programming easy.
    No it doesn't. It makes some aspects of programming easier, notably memory management, but that's it. I don't think there are many people who can write good code in those languages but are incapable of writing good C code. It's just that it's less obvious when bad code is written in those languages, so a lot of utter incompetents get away with passing themselves off as programmers.

    When C code is written poorly, it either won't compile or it crashes obviously; whereas when PHP (for example) is written poorly, errors are not immediately obvious (they only come to light through testing, as there's no compilation stage), and bugs are more likely to take the form of abysmal performance, incorrect behaviour, or massive security problems, than anything obvious like actual crashing.
  79. Re:And older firefox versions do better too by Runefox · · Score: 1

    Which of the two released version, 6.0 and 7.0 are beta, exactly ?

    Neither. They're both alphas. =D
    --
    Screw the rules, I have green hair!
  80. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    Ah, but I'm not an employee, I'm the owner. Not only have my clients never seen the t-shirt, but they wouldn't understand it if they did. My clients are non-technical, it doesn't matter how "properly" the code is written, or even if it's written at all. The product either works or it doesn't, and as long as I'm accountable for it, that's all that matters. They aren't purchasing the code -- half the time they don't even get access to it. They're purchasing the accountability that I provide with the product/service.

  81. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    Ah, welcome to democracy. That's how it works.

    And really, it's not selfish. It's self-serving, of course, but it's not selfish. I'm supporting family, friends, contractors, clients, employees, all of their families, and my dog. If you're saying that I'm not considering _your_ interests, well, that makes you selfish.

  82. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    That was a very responsible thing for you to do.

    Or, you could have actively kept the electronics industry from moving forward, and maintained your existing way of life. Sure it would have been worse for society, but it may have been better for you.

    Now, you may not have had the strength to do that. But I'm not alone in my views, and I've got some of the largest companies on my side of this particular fence. I'd prefer that things not progress forward.

    That's my vote. You are welcome to yours.

  83. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    Umm, I don't know what you think my 12 year-old self is worth, but my 12 year-old self did well enough to bulid a business out of nothing. I competed with people bigger than me then (which pretty much meant everyone), and I continue to do so now.

    A current 12 year-old who mirrors my 12 year-old's character would have no trouble competing with me today. That is the very nature of my 12 year-old's character. There are always cracks and fissures in anyone's client base, and there are always ways to sell to that market and to exploit that industy. I now gloss over the type of client that used to be my bread and butter. In order to get here, I had to pull my current client type away from other vendors. Welcome to competition.

    I fear today's 12 year-old entrepeneur the same way other vendors have feared me for the last 20 years -- or should have.

  84. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    I would argue that technology is the largest part of the economy when you include everything that was "technology" when it started. That would include what is now $6/hour metal working.

    What you are asking me to do is to shift my focus from product quality to product sales in an effort to compete in a larger industry for more programmers and such. That's simply not of interest to me. I'd much prefer to focus on product quality in a smaller industry -- the one that currently exists.

    And yes, I do see browser standards as one of the many things that would change this industry. So yeah, not only will I not support it, but I'll support it's opponents. And just like you support those standards, I believe that my support has some meaning and value.

    But also, I don't have win out-right, I simply have to win in the relative sense that you describe. Delaying it for even a few years goes a long way in my business.

    My clients tend to use my products to grow their business in ways that are not ROI related. And they can either afford to make it happen or they can't. It's not a matter of pennies one way or the other, it's a matter of a few thousand in any direction. I get to flex that in order to trump larger corporations on the same bid. I currently benefit from being near the bottom of that particular pack because my clients aren't really willing to go with anyone smaller, and very few of those smaller are able to achieve the project goals in the first place. I operate at the top of my company's abilities, not in the middle. I don't want little guys to be able to creep in.

  85. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    You've mixed up my points -- or I've mis-used some punctuation. I don't choose to maintain my company's status quo, I choose to hold back the industry as much as possible -- there's a difference.

    Also, I do choose to develop high-quality products. I can do so now because it's my product quality that competes in my industry. But if this industry grows, then the quality doesn't matter as much. Then I'll have to start competing on price alone. Which means that my focus turns to sales, and away from quality. That's when my quality changes.

    And I don't have to be "supremely worried about competition" to recognize that competition is a bad thing for vendors in my current industry at this time. I'm not about to support something that hinders me just because it only hinders me slightly.

    Incidentally, I certainly understand that the views I've expressed are contrary to the norm, especially around here, and that's all fine and good. But without having done anything more than expressed my business objectives and decisions, I don't think a negative moderation is appropriate. This isn't even my opinion, it's my actions in the industry. By moderating down to the point where many won't see it, well, that's just obscuring information which may or may not be relevant to a reader. I note this as a point of interest, as it works to quickly render the moderation points into "agreement points" instead of "value points". Maybe meta-moderation will fix that in the next few days.

  86. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    Yup, and that lets more "programmers" vie for your clients, than if everyone had to be fluent in C. But hey, I have one example for you. I started in C/C++. I quickly left and went to Perl because I got sick of absolutely everything being memory-related.

    And yes, you are 100% correct when you say that all of my Perl bugs wind up being performance issues and security issues. And I actually get to sell that as a benefit to my clients saying things like tehy can pay less and get it sooner if tehy don't care about security and performance. And a good half of my clients are working on projects where they really don't care. So I get t oweasel a real C/C++ programmer out of the job because I'm using an inferior language.

    That was especially the case back when I was 12. Now, I've built up my techniques, convensions, and platforms to have the security and get most of performance back, still have the benefits of Perl plus the benefits of my own platform. But I've balanced a little the other way and so it takes me a little bit longer than it used to. That leaves room for my former self to grab jobs away from me. Right now, I can debate that by saying that I'm building much larger and more cross-integrated features than my former self could. But browser standards would assist my former self more than it would assist me.

    Actually, that's what ActiveX did for me. I used to be unable to make use of peripherals like barcode scanners, card readers, printers, turnstiles, and the like using Perl. I'd have had to use C++ in order to make use of the drivers and libraries to interface with those items. Then, a few years back, I started finding drivers with ActiveX OCX controls. So now, without any C effort at all, I can control business peripherals with ease. That's one more thing that a C++ programmer can't use to explain why his business is a better choice than mine.

  87. Re:And older firefox versions do better too by edwdig · · Score: 1

    Probably because your post gave the impression that you were surprised that the current versions scored terribly.

  88. Re:You shouldn't be supporting standards by bandersnatch · · Score: 1

    My point was that it's not the customer that pays the bills, it's the customer's employer that pays the bills. That is my point.

    Frankly, in the global economy with the complexities of international ownership and investment, if the "employer" and "employee/customer" in your argument is limited to a strict national basis, particularly for a major industry (we are not talking about Mom & Pop outfits here) they are both screwed and if they are inefficient, they are doubly screwed.

    Because that $200'000 cd player was made here in Canada/U.S.. But your $25 player that you have now, came from Taiwan. So you've given $25 of your economy's worth away to another country, another culture, and to other people. You've exported cash. You've eliminated jobs.

    The economy and the job market are not zero sum (I refuse to call it a game). Yes, there are real people affected with one whole segment of the economy goes and is replaced by something/someone/somewhere more efficient. However, that is hardly a reason to specifically build in inefficiencies (or non standards compliance) into the goods/services we produce in the hope that no one else will offer anything better and/or cheaper. There are a few lucky exceptions (usually due to regulations(safety, secrecy, make work, trade barriers, etc), but in general the market (or human nature if you prefer) will route around you and leave you high and dry quite quickly.

    I suppose it's possible to "raise awareness" as in the various "Made In *" programs, but frankly that's not business, it's charity.
  89. Re:You shouldn't be supporting standards by holophrastic · · Score: 1

    I agree with :"that is hardly a reason to specifically build in inefficiencies", but that doesn't mean it isn't worth supporting those inefficiencies when they are already there.

  90. Just hold on..... by namco · · Score: 1
    Did ANYONE, properly, read TFA??

    You guy's call yourselves geeks, and all I see in the comments section is ramblings about differences in IE versions and no one mentioned the one obvious anomoly in Windows OS's compared to the respective IE versions??

    In TFA:

    Internet Explorer 5.50.4807.2300 (SP2) Windows XP Service Pack 2 (Multiple IE) 14%
    Internet Explorer 5.50.4134.0600 Windows ME 14%
    Internet Explorer 5.50.4807.2300 (SP2) Windows 2000 Service Pack 4 13%

    Internet Explorer 7.0.5730.13 Windows XP Service Pack 2 12%
    Internet Explorer 7.0.6000.16609 Windows Vista (32-bit) 12%

    Internet Explorer 6.0 Windows XP Service Pack 2 12%
    Internet Explorer 6.0 Windows 2000 Service Pack 4 11%

    Why does an older OS (Win ME), with an older version of IE5.5, perform better than W2K SP4 with the newest version of IE5.5, compared to Windows XP with the newest version of IE5.5??

    That doesn't quite make sense. We all know that IE is integrated into windows OSs but if an older version of windows on the 9x version of architecture performs better than, arguably, *one* of the more better built operating systems, what does this say about both IE AND Windows OS's in general??

    Secondly, why hasn't the author of TFA included which service pack of IE 6 they are using like they did with IE5.5?