Slashdot Mirror


Opera Lays Down Acid2 Challenge

sebFlyte writes "The CTO of Opera has proposed a new version of the acid test for browser compatibility, and has challenged Microsoft to make IE7 a browser worth having that will do the Web good. He's asked to help from Web designers the world over to build a new page for Microsoft to test IE7 with to make sure it does everything Web designers want it to. "

38 of 499 comments (clear)

  1. Like, render Slashdot the same way every time? by ScentCone · · Score: 4, Funny

    *cough* Firefox

    --
    Don't disappoint your bird dog. Go to the range.
    1. Re:Like, render Slashdot the same way every time? by porcupine8 · · Score: 4, Interesting

      Am I the only person who has never had any issues with slashdot and firefox? Or if there are, they're minimal enough that I've never noticed them, so I doubt they're really worth bitching about.

      --
      Warning: Apple/Nintendo fangirl. Likes her electronics cute & cuddly. May be rabid.
    2. Re:Like, render Slashdot the same way every time? by Jerk+City+Troll · · Score: 4, Interesting

      View the source on any Slashdot web page and observe the gigantic, sloppy cluster-fuck that is their output. Do not blame Gecko for this nightmare of deeply nested tables, font tags, missing close tags, and other crap. (What's funny is that Slashdot gives an HTTP 403 to validator.w3.org.) When Slashdot makes their code sane, then we can blame the browser. It's amazing to me that any user agent can parse this and make sense of it.

    3. Re:Like, render Slashdot the same way every time? by ptlis · · Score: 4, Informative

      I too suspect it is in some way related to the iFrames - when I run Firefox without AdBlock I get the errors very regularily (a rough guestimate would be something in the region of every 10-15 page views) but with AdBlock blocking the OSDN ads the problem seems to go away (or at least it occurs very rarely).

      --
      There's mischief and malarkies but no queers or yids or darkies within this bastard's carnival, this vicious cabaret.
    4. Re:Like, render Slashdot the same way every time? by say · · Score: 5, Informative

      What's funny is that Slashdot gives an HTTP 403 to validator.w3.org

      I saved the source of this comment page and fed it to the validator. Made 117 errors, among them a fairly serious one:

      Line 2007, column 7: end tag for "TABLE" omitted, but its declaration does not permit this

      It also has _tons_ of unclosed LI tags. These obviously can mess up the display quite a lot. Except for that, the errors are mainly cosmetic - & instead of & and some spurious attributes which aren't in the 3.2 standard (nobr, iframe height etc.).

      The missing </table> is probably the most serious issue.

      --
      Roses are #FF0000, violets are #0000FF, all my base are belong to you
    5. Re:Like, render Slashdot the same way every time? by arkanes · · Score: 4, Informative

      Slashdot declares HTML version 3.2, and the w3c validator is actually much stricter than the written standard. For example, you don't need to close LI elements, as they are implicitly closed by the next LI element. Same with non-standard attributes and even tags - the spec explicity defines behavior for undefined attributes and tags, which is a no-op. It should be a warning that you may be relying on non-standard behavior, but the standard does not prohibit them. Even the missing table end tag may be permitted under the standard, although I'd have to do some digging to check. There's something about block level elements and implicit closing by a new block element that I'd have to get the exact wording on. It's why you don't need a close tag for P elements in HTML 3.2, for example.

  2. Why just microsoft? by MoneyT · · Score: 4, Insightful

    Has anyone (even Opera) managed to create a browser that does what all the web designers want it to do? Does the web designer community have a consensus of what they want the browsers to do?

    --
    T Money
    World Domination with a plastic spoon since 1984
    1. Re:Why just microsoft? by Pionar · · Score: 4, Insightful

      Yes, it's called W3C specifications.

      Like the one for xHTML 1.0. The one that currently has IE in my doghouse is CSS2 support, especially the Box Model. Firefox gets it right. Opera gets it right. But IE gets it totally wrong, forcing web designers to use unsightly hacks to get CSS to behave the same way in IE.

      The web community has always had this consensus, going back to HTML 3.2 and even further back. It's the browser makers that can't seem to come to a consensus, which is ridiculous because the W3C tells you how a user agent should behave.

    2. Re:Why just microsoft? by Pionar · · Score: 3, Insightful

      Since IE is the standard broswer for computers, isn't being compatable with IE the defacto standard for websites? Therefore shouldn't other browsers conform to MS standards?

      No. Web people have worked very hard to come up with standards (MS is even on committees in some of these areas). Standards make it easier for someone to create something once and not have to worry about what platforms it works on. One of the hardest parts of any web developer's job is to troubleshoot why webapp X won't work in browser Y. Thankfully, IE is pretty much there with the DOM, but CSS support is still lacking, and it's riddled with rendering bugs.

  3. "acid" by hey · · Score: 3, Funny

    You can usually remove the word "acid" from "acid test" without doing any harm.

  4. The acid test should answer the question... by Faust7 · · Score: 4, Funny

    Will IE 7 have 'Electric Kool-Aid' tags?

  5. Implementing full standards would help by PornMaster · · Score: 4, Interesting

    It'd be nice if there were reference pages made by the standards committees, so a browser could be simply deemed compliant or not.

    1. Re:Implementing full standards would help by bersl2 · · Score: 5, Informative
  6. Why Bother? by djrosen · · Score: 3, Insightful

    MS has never shown the initiative to make things compliant why should any developers waste precious time coding a page for MS to balk at when there are other browsers out there? Firefox is slowly but surely gaining market share. I say Good Riddance to IE and make room for the new guys. Why HELP MS strenthen their hold?

    1. Re:Why Bother? by jbplou · · Score: 4, Insightful

      If you are making a web page and you are not coding so that is renders correctly on IE you are a fool. It has 85% market share.

    2. Re:Why Bother? by Low2000 · · Score: 5, Insightful

      Because if IE becomes more standards complient, that means that web coders will make their websites standards compliant. Thats good for the alternative browsers out there like Firefox and Opera more then anyone else. MS has enjoyed being in control of the bulk of the web browsing community for so long that if their browser doesn't conform to standards, the web coders have to conform to the browser.

  7. Meanwhile..... by Eradicator2k3 · · Score: 4, Funny

    Microsoft's IE7 developers allow themselves a chuckle and think, "Ha! We've been on acid for decades."

    --
    Mr. T pitied this fool on 27 July 1992.
  8. Standards, schmandards... by glamslam · · Score: 4, Insightful

    Standards compliance is for companies that don't have 90% or more of a market.

    Next!

    1. Re:Standards, schmandards... by rcamans · · Score: 3, Insightful

      I believe market refers to a place where you must pay for goods.
      I use the term "goods" loosely, here seeing as MS stuff should be termed "bads"
      But when you can get the same stuff for free, then the customer who pays is usually refered to as gullible, and the seller is often refered to as a con man.
      Don't they have laws against cons?
      Oh, wait, that law only applies to the little guys who con.
      Big guys who con are refered to as successfull monopolies.
      Never mind.

      --
      wake up and hold your nose
    2. Re:Standards, schmandards... by SpecBear · · Score: 3, Insightful

      Yes, indeed. As Netscape showed us, once you have a lock on the market the browser war is over and you don't have to improve your product at all.

      By the way, IE had 90% of the market. It no longer does. The problem with the monopoly position is that it makes MS complacent. If your browser is free, installed on almost every PC sold, and is the standard that most developers code to (even when it violates the W3C spec), then you really have to suck before people besides hard core geeks switch to something else. Once that starts happening, it means you've been sucking hard for a good long time and you've got a lot of catching up to do in terms of features and good will.

  9. Great Strategy by aspx · · Score: 4, Insightful

    This is brilliant!! Appear to be helpful, but really just point out shortcomings and bugs in your competitor's product, all the while gaining visibility and recognition in the community. I really must remember to do this sometime.

  10. I want IE7 to... by Mr.+Flibble · · Score: 3, Funny

    Load even more spyware!!!

    Err, oh. I guess that that was not a valid choice.

    --
    Try to hack my 31337 firewall!
  11. Re:IE not worth caring about by stupidfoo · · Score: 3, Insightful

    Is anybody actually caring about IE at this point?

    Why would anyone care about the experience of 90% (or whatever) of the site's users?

  12. Why take up the gauntlet? by Fjandr · · Score: 4, Insightful

    Microsoft would more than likely simply ignore the challenge completely. What do they have to gain (at this point) from actually producing a standards-compliant browser?

    Now, perhaps if FireFox continues to chew up the percentages of web browser usage, they might try it for PR purposes, but that's hardly an issue at the moment. Microsoft is more of an in-the-moment company (unless you're speaking of up-and-coming products, where they announce competing programs years before they actually plan to implement the changes).

  13. Re:Like say the same joke everytime? by Anonymous Coward · · Score: 3, Funny

    As opposed to a real name like ScentClone! Thank god we can trust you.

  14. My proposal for the test page. by bigtallmofo · · Score: 4, Funny

    I humbly submit my idea for building a new page for Microsoft to test IE7 with to make sure it does everything Web designers want it to.

    Get Firefox!

    If it can properly render that link, I'll be satisfied.

    --
    I'm a big tall mofo.
    1. Re:My proposal for the test page. by _xeno_ · · Score: 3, Funny

      Worked fine for me, what problem did you have with it?

      --
      You are in a maze of twisty little relative jumps, all alike.
  15. Test suites by cortana · · Score: 3, Interesting

    Aren't there test suites that test the conformance of an implementation to all aspects of CSS2 standard already? And if not, why not?

  16. Re:Opera by QuietLagoon · · Score: 4, Insightful
    Opera is hardly the bastion of interoperability.

    Correct. However, Opera is falling behind in mindshare now that FireFox has all the buzz. So the best thing for Opera to do is to put up a standards challenge to Microsoft.

    That accomplishes two things: (1) some free PR for Opera, and (2) if anyone really follows through with it, it is far easier for Opera to adapt to the results than Microsoft. Opera has only a miniscule installed base that it needs to stay compatible with.

  17. In other news... by wannabgeek · · Score: 3, Insightful

    Open Source geeks challenged M$ to make windows the most secure OS.
    US challenged China to be most democratic country
    blah blah

    Mod me down as troll, but what makes anyone think M$ cares about a challenge from a competitor?!

    --
    I'm much more funny, interesting and insightful than the moderators think
  18. Wrong target by whitehatlurker · · Score: 3, Interesting
    While it would be nice if MS IE 7 were a more compliant browser, the real target is the lazy web authors who do not try to comply with standards.

    Or the malicious ones who miscode their site to intentionally over-support a browser.

    I support Hakon, but I think he's aiming at the wrong spot.

    Caveat: I have used (and liked) Opera since version 3 or so. I am have used (and hated) IE since version 2 or so. I am hardly unbiased.

    --
    .. paranoid crackpot leftover from the days of Amiga.
  19. opera? bloatware? sinks? .. that reminds me... by xlurker · · Score: 3, Funny
    ... before it's time to cement IEs feet and dump it in in the ocean.

    it's not over till the fat browser sinks, eh?

    haha, I kill me... *snicker*

    --
    ______________________________________________
    sigamajig...
  20. Re:Opera by bogie · · Score: 4, Insightful

    FWIW last time I checked Opera was pretty much tied with Firefox for being standards complaint. Among browsers that normal human use that's saying a lot.

    Based on that I don't see what's laughable.

    --
    If you wanna get rich, you know that payback is a bitch
  21. Re:Opera is already dead. by badmammajamma · · Score: 4, Informative

    Actually they make quite a bit of money selling Opera. It's used a lot as an embedded app in cell phones, PDAs and such. As I understand it, Opera runs on more devices than any other browser. They also are more than willing to make custom versions for just about any platform or purpose.

    Any money they make from people sitting in front of desktops is just bonus.

    --
    Any man who afflicts the human race with ideas must be prepared to see them misunderstood. -- H. L. Mencken
  22. Sometimes, IE renders bad HTML well by benhocking · · Score: 4, Interesting

    This is not meant to be an attack on IE. If reasonable assumptions can be made about what the code should do, even when coded incorrectly, then it's great that IE does this. I'm not sure of any specific examples, but when I first started writing web pages (years ago), I remember that Netscape would cough on some pages that IE rendered well. Invariably, the problem was that I had left off some terminating tags, and IE correctly figured out my intentions.

    Three caveats:

    First, having Netscape scold me allowed me to fix my code. IMHO, a better way to do this, however, would be to have an option called "pedantic" that would insist on matching tags (where appropriate). This might exist now, and if so, that's great.

    Second, trying to "guess" what was intended is rife with problems. Anyone who has used MS Word for long enough knows what I mean.

    Finally, I currently use FireFox the vast majority of the time. I do not know if any of what I said is still true.

    --
    Ben Hocking
    Need a professional organizer?
    1. Re:Sometimes, IE renders bad HTML well by Anonymous Coward · · Score: 4, Insightful

      Browsers shouldn't render broken HTML.

      Compilers shouldn't compile broken code.

      If, as a programmer, you think that a compiler is better because it will compile buggy code without errors then god help you.

      The same applies to web design. Buggy HTML might render OK as just HTML, but once you start adding CSS into the equation (and IE has its OWN little array of bugs here) then it can start causing severely bizarre behavior.

    2. Re:Sometimes, IE renders bad HTML well by ChatHuant · · Score: 3, Informative

      Browsers shouldn't render broken HTML.

      Compilers shouldn't compile broken code


      Compilers shouldn't, because their user is a developer and he can (and should) fix the problems. But browsers should indeed render broken code, or make a best effort thereof. It's called graceful failure and it's a very important characteristic of production-strength software.

      The user of the browser isn't the web page developer, and he isn't interested in the minuties of CSS and W3C standards. The user wants to see the page, and the browser should show it to him instead of crapping out with weird and useless errors.

      We could argue that a resilient browser encourages bad code development habits. That may be true, for bad or amateur web developers, but it's still not the fault of the users. There are tools and validators that allow good devs to check the correctness of their code and fix it before deployment.

  23. Re:Opera? Compatibility? by joebp · · Score: 3, Informative

    XMLHTTPRequest is not specified in any standard. It's more Microsoft extension nonsense which Mozilla foolishly embraced. Then again, the Mozilla guys tend to make poor decisions (hello IDN!)