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

40 of 499 comments (clear)

  1. 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. Re:Why just microsoft? by MoneyT · · Score: 2, Insightful

      But again, the question was, whose standards do you align to? If one way of doing X conforms with IE and it's standards, and another way complies with W3C, which way is the standard if IE doesn't conform to W3C? W3C may call it a standard, but IE is the browser people are using and as far as the users are concerned, if it doesn't work with IE, it's broken. Not the other way arround.

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

      I think the major issue here for most folks is that HTML4, CSS2, and other standards are non-proprietary standards created by an independent standards body. While few browsers are or have ever been 100% compliant on EVERY DETAIL of a published standard, only Microsoft (of the remaining major broswer vendors) has a history of DELIBERATLY ignoring standards or DELIBERATLY incorporating non-standard extensions into their browsers. They've been doing this since IE 1.0.

      Why just Microsoft? Because they're the only one who's shown the propensity for ignoring open standards and trying to create their own related-but-proprietary substitutes.

      And, no, I'm not a knee-jerk "Microsoft sucks!" person. But the history here speaks for itself.

    5. Re:Why just microsoft? by grungefade · · Score: 1, Insightful

      I think mainly web designers just want browsers to be consitent.

      I for one support this 100%. It would be great to have a master page that every browser used as a template to make sure everything is rendered correctly.

      As a web designer myself, there is nothing more fustrating than getting in the heart of CSS and trying to make your entire sites layout and design with CSS. You constantly run into problems like, in one browser it displays 2 pixels over, and in another its 3 pixels. Or margin height works in one and not the other. Sounds like a small problem but when you run into lots of those type of issues you have to find work arounds to make them look correctly, or shall i say look decent in every browser.

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

    3. Re:Why Bother? by dotslashconfig · · Score: 2, Insightful

      You're either joking, or you're a moron.

      Let's deal with the joking option first:

      Internet Explorer may not be the best browser, but it's the one most individuals (read: people who buy computers from CompUSA/Dell) are likely to use - simply because it's there and it's supported.

      Now the moron option:

      "Slowly but surely" is the most bullshit phrase in the English language. A pretty strong argument could be made that the Internet Explorer crisis is at its peak right now. It has had a number of years as the front-runner, and almost exclusively used browser in the world. Virus and malware writers have had time to examine and exploit IE to its fullest. Despite this fact, adoption of alternative browsers hasn't happened en masse (see "joking" argument above). Thus, the slow adoption of Firefox could potentially come to a halt should Microsoft remedy even 1/3 of the issues plaguing Internet Explorer.

      Saying "good riddance" to IE is like forecasting the rapid adoption of Linux/Unix/OSX. Just because there are sometimes better alternatives doesn't mean that the current dominant force will suddenly vanish. In any case, Firefox adoption wouldn't happen all at once, and certainly not all within the next few years, as you seem to imply will happen.

    4. Re:Why Bother? by mgpeter · · Score: 2, Insightful
      Saying "good riddance" to IE is like forecasting the rapid adoption of Linux/Unix/OSX. Just because there are sometimes better alternatives doesn't mean that the current dominant force will suddenly vanish. In any case, Firefox adoption wouldn't happen all at once, and certainly not all within the next few years, as you seem to imply will happen.

      Back in the late seventies, early eighties the same thing was said about Atari, there were better alternatives back then but everyone wrote games for the 2600 anyway. Once people started to realize there was better alternatives, Atari all but vanished. Granted Microsoft is "innovating" more than Atari did back then, but once developers start porting their apps to ANYTHING other than Microsoft, people will turn to something else.

      I still get a kick out of watching Blade Runner and seeing all the Atari signs and billboards plastered all over the place.

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

      I tend to treat IE as a crappy baby I have to babysit. I make sure it renders my pages okay but I don't try to let it play with the adults. So I can do nicer things on my standard stylesheets than the variant IE is made to use. I don't waste a lot of effort trying to make it do all the bells and whistles.

      --
      At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
    6. Re:Why Bother? by jbplou · · Score: 2, Insightful

      You have a very specific example. But in the real world, releasing a site to the general public it must be fully usable by IE. I worked at an ISP doing tech support a few years ago and you would not believe how many customers thought Internet Explorer is the only way to access the Internet. You might say they are dumb then, but hey if your trying to sell a product or get information out you need to reach as many people as possible. Now that is a good example for training to show differences in browsers, by the way Opera has standards problems as well.

    7. Re:Why Bother? by slackmaster2000 · · Score: 2, Insightful

      I don't think that particular issue would be part of any web standard. How the browser handles file downloads and interacts with the operating system is up to the browser.

      I've actually had to work on the specific problem of making IE download files instead of open them, and found that it certainly is possible, just tricky. It's just as tricky to get other browsers to handle files the way IE does when you want them to, but it's also possible.

      Regardless, blaming Microsoft because your application doesn't work in IE is just as lame as blaming Mozilla because I can't pay my cable or cell phone bill with Firefox.

      Life is full of "how things should work vs. how things do work." Being successful requires that you make things work. Crying about how things should work to justify your widget that doesn't work isn't going to get you very far.

      I don't like IE either. I wish it would die. I've switched dozens of people to Firefox. When I develop I test on Firefox first, but the second browser I try is IE. Not testing on multiple browsers is a practice that should have died off in the early nineties.

    8. Re:Why Bother? by dodobh · · Score: 2, Insightful

      Or IE is just not in your target market.

      --
      I can throw myself at the ground, and miss.
  3. 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 discordja · · Score: 2, Insightful

      Considering even Microsoft IE6 does not have a 90% market share anymore that doesn't include them either.

      --
      I stole this .sig
    2. 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
    3. 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.

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

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

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

    1. Re:Why take up the gauntlet? by rpdillon · · Score: 2, Insightful

      Well, right now, it's hard to explain to someone that doesn't know the backstory why "standards" are a Good Thing. If we had a web page made by web designers that would show off how things SHOULD look (put jpegs of the correct rendering beside the code), you could give people a location to visit to objectively measure their browser.

      This is important, because if Opera, Safari, Firefox, Konqueror, et. al. all render it fairly closely, and IE mangles it, you then have a story. CNet will run it, CNN will run it, and Slashdot will have a story pointing to the other stories: "IE7 Proven to Have Shitty Rendering Engine". Right now, there is no story, because the public doesn't understand the "standards" mumbo jumbo. But even a brand new user can understand two pictures not looking the same.

      "I visited http://isyourbrowserhotornot.com and it looked totally messed up! What can I do?"

      "Go download Firefox."

      Basically, this gives some kind of ruler an end-user can use to measure a browser in a fast, objective way. Right now, we either don't have that, or it is not well known. This puts the pressure on Microsoft to become more standards compliant. If people become *aware* of IE's shortcomings, they will be more likely to switch. If they don't become compliant, they will continue to steadily lose market share. If they do become compliant, they lose their strangle-hold on the market and everyone wins; we're back to no-browser-monopoly. Yea! Choice is good.

  7. Opera is already dead. by Saeed+al-Sahaf · · Score: 1, Insightful
    Honestly, what is the point to making "challenges" to Microsoft to bring their browser into the fold of standards compatibility? This is not news. This is hype for Opera, a browser that is a commercial product looking for customers that are not there. Standards compatibility is something that all applications should look to meet, thanks Opera for telling me this nugget of wisdom.

    Question: Is Opera looking for market? Basing your business model on selling a web browser is not going to make it. Note to Opera: Application Platform. Or die.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
  8. 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.

  9. Yeah, so... by gbulmash · · Score: 2, Insightful
    This is not the first challenge the Opera folks have issued to M$ and most likely not the last. It seems that the heads of Opera have a bit of a quixotic relationship with the windmill of Microsoft.

    And let's not be smug about everyone but Microsoft following standards. The company I used to work for had a file-upload javascript that worked with Firefox, Mozilla, Opera, and IE, but it didn't work with Safari and we had to specially recode the script just to accomodate that Safari quirk.

    It would be nice if every page rendered the same way on every browser, but let's be real. There will still be millions and millions of people who are slow to upgrade. Even if the latest versions of Opera, Firefox, Safari, and IE join hands in a circle and sing Kumbaya, you're still going to have to test your sites on Netscape 4.7, IE 5, etc. or you're going to have issues with the 30-40% of the market who hasn't upgraded yet.

    - Greg

  10. 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
  11. Re:Opera by Anonymous Coward · · Score: 1, Insightful

    Ha, I was thinking the exact same thing.

    Plus it crashes all the time and costs twice what it should ($40 for a freakin web browser?! what's next, a $40 terminal emulator?).

  12. Why would Microsoft care? by winkydink · · Score: 1, Insightful

    Opera is an increasingly marginalized player in the browser market. The only thing Opera can expect to get out of this is a little PR that only delays the inevitable for them (non-player).

    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

  13. 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
  14. The Issue... by Anonymous Coward · · Score: 2, Insightful

    Most people are not web designers.
    Most people are not familiar with the nuances of CSS2.
    Most people are not aware of the various published spec's from W3.
    Most people are users.
    Most users use IE.
    Most people percieve "what the web can do" to be what they've experienced as "what IE can do."
    Most people don't know what they're missing.

    "What Microsoft provides" is already the de facto standard for the web. And most designers are resigned to living with this--nobody puts out CSS2 elements that IE does NOT support on production pages.

    There's zero pressure on Microsoft for standards compliance. Most people can barely comprehend the technical nuance of what the weberati say is "noncompliant," let alone be up in arms about it.

  15. Hrrrmpph! by thegnu · · Score: 2, Insightful

    Even though it sounds a little tinfoil-hattish, the fact that a non-standards compliant web browser dominates the market might have a whole heck of a lot to do with all those web pages that don't follow standards, and rather choose to be compatible with IE.

    --
    Please stop stalking me, bro.
  16. Re:Like, render Slashdot the same way every time? by rsborg · · Score: 2, Insightful
    That being said, I think some sort of Ultimate Browser Agony Test is a good idea. But to suggest that it's somehow Microsoft's fault that we need one is, well, just dumb.

    Nothing dumb about it. Micrsoft has thumbed their nose at standards for the past 10 years, and the mess that is web standards is due mostly in part to the way IE (with > 90% marketshare) fails to adhere to those standards. Oh, and btw, if you haven't forgotten: Microsoft is a convicted monopolist in more than one continent. That means it's illegal for them to do shit like engineered lack of interoperability.
    But some people keep apologizing for them (sigh).

    --
    Make sure everyone's vote counts: Verified Voting
  17. Microsoft has everything to WIN here, not lose by iamsure · · Score: 2, Insightful

    Microsoft is constantly competing with itself, not others. It needs people to buy the latest versions of its OS and applications (office) to keep revenues coming in.

    As a result, it chooses to do things like release the XP2 firewall but not offer it for win2k - to push people towards newer versions, despite win2k being in mainstream support.

    Recently, they've been forced by the HUGE number of corporate customers to offer WinFS as an option for XP as well as future versions of the OS. Why? Because corporate customers don't run bleeding edge software.

    So what they need is a huge, wonderful carrot that will lead customers to the latest version. We arent talking about Dear Old Aunt Sally - she doesn't buy new versions of OS's. She buys a computer, and it comes with it.

    We are talking about corporate customers. They didn't buy the concept that WinFS couldn't work on XP, but Microsoft has been shouting (even swearing in court) that the browser is part of the OS.

    As a result, MS could very easily make IE7 only available on longhorn. As such, it's an opportunity for them to make it a selling point - a carrot.

    To make the carrot more attractive, they need to make it do as many things RIGHT as possible. If IE7 truly supported css2, png transparency, javascript, and so on, WEBDESIGNERS would start drawing the line at older versions of IE - doing Microsoft's selling for them!

    Businesses, portals, and the list goes on - anywhere that wants to make a truly compelling site without a million css box model hacks would start suggesting users use IE7, and before long, REQUIRING IE7.

    Microsoft has every reason in the world to kick major standards-ass with IE7, but unfortunately, they have a track record of not doing it.

    Here's hoping that their business savy is more powerful than their laziness. :)

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

  19. Re:Sometimes, IE renders bad HTML well by Anonymous Coward · · Score: 1, Insightful

    > Frankly, if IE handled the 'Box Model' correctly, for css....it would be a HUGE improvement

    It does, IF you use the strict DTD. Anything else goes into "quirks" (i.e. broken) mode. The parts that are still broken are the parts that are pretty ambiguous to begin with.

  20. Re:Why just microsoft? [Everybody sucks sometimes] by EtherAlchemist · · Score: 2, Insightful


    In short, no.

    Even if someone makes a browser that does everything designers AND developers want it to, it still won't do any good to those of us stuck supporting browsers that DON'T do all of it. The entire world is unlikely to switch instantly to the new wonder browser, leaving us to support legacy products.

    Where I work our top tier browser/OS matrix is:
    Win 98 - XP; IE5>, Mozilla 1.3>, Firefox 1>, Netscape 6.2>
    Linux; Mozilla 1.3>, Firefox 1>, Netscape 6.2>
    Mac OSX; Safari, IE 5.3>, Mozilla 1.3>, Firefox 1>, Netscape 6.2>

    This is a nightmare to build, even worse to QA. Opera, ironically enough, is not in our top tier BECAUSE it rendered pages differently enough from the other browsers- even though we were authoring XHTML 1.0 trans and CSS2 compliant- that it got shunted to a lower tier of support.

    If you pick any of those, IE would be the worst example, you can get different implementations between versions of how a page is supposed to render.

    I think this is why a large portion of the pages on the Web are authored they way they are- the broadest reach for the narrowest buck.

    Mac isn't the only brand with a cult. Build the world's best browser and you'll still have legions of people SWEARING that their choice in browser is the best, and pages that look like shit in it are due to the page not being written correctly rather than the browser's render engine using its own interpretation of WHAT the page is SUPPOSED to look like

    On the cynical side, I think a browser that did everything that Web designers wanted might come out something like Homer's car.

    Or Opera.

    --
    R(k)
  21. Re:Like, render Slashdot the same way every time? by cosmo7 · · Score: 2, Insightful

    The thing I don't get is why not use CSS? I'd have thought the bandwidth saving alone would be reason enough, let alone cleaning up all the drunken formatting.

  22. Re:Like, render Slashdot the same way every time? by JediJorgie · · Score: 2, Insightful

    I see it all the time with FF1.0.1 (with or without extensions). And when it happens, you CANT ignore it because the page is unreadable... But the fix is quick... change text size. I just hold CTRL and bounce my scroll-whell forward and back.. It has gotten to the point that I don't even think about it, it is just reflex.

    Next time you are reading a /. story about bad programming, take a second and do a view source.. :)

    Jorgie

  23. Re:Like, render Slashdot the same way every time? by jacksonj04 · · Score: 2, Insightful

    I sense a chicken-and-egg coming along here.

    The solution is obviously starting to show here, write sites to the standard and browsers will follow.

    --
    How many people can read hex if only you and dead people can read hex?