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

499 comments

  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 Anonymous Coward · · Score: 1, Informative

      Or keep your stable release and install SlashFix.

    3. Re:Like, render Slashdot the same way every time? by LiquidCoooled · · Score: 1

      They are horrendous.

      I believe its something to do with the timing of the advert iFrames, but I could be completely wrong.

      Do you perhaps filter out all frames with some kind of proximatron type software? or do you not filter your html in any way?

      --
      liqbase :: faster than paper
    4. Re:Like, render Slashdot the same way every time? by ScentCone · · Score: 2, Interesting

      Actually, I use Firefox all day long, even though I frequently turn to MSIE for some testing or specific corporate sites. I build pages for a living, and I've a long, long list of gripes about every browser, in every version. Opera in particular seems to give some table nesting some trouble that IE doesn't exhibit, but all things considered, I'd rather use FF. There's a lot of pot-calling-kettle-black about the Opera challenge, that's all. All of the kettles and pots are black. 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.

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

      I don't even know what proximatron means. I just downloaded and installed Firefox, and started browsing the web. It looks a tiny bit cramped, but I think that has more to do with my work monitor's resolution (which is lower than at home, where I use Safari).

      --
      Warning: Apple/Nintendo fangirl. Likes her electronics cute & cuddly. May be rabid.
    6. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      Yeah, Firefox has rendered Slashdot pretty badly for my since around 0.7 I think, give or take a .1. I don't see it anymore with SlashFix installed, but made me wonder why they waited so long to fix it! I keep hearing it was part of the main trunk, but this problem has been around for a long time. Maybe the devs don't read Slashdot...

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

    8. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      Slashdot renders fine if you're on acid, I hear.

    9. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      Lots of people have this problem, and in my case it happens just about every time I load the page. The comments are flush with the left side of the window, so the comments completely overlap the navigation bar on the left. People say "quit bitching" and whatever else, I guess it's too much to ask for Firefox to work correctly.

    10. Re:Like, render Slashdot the same way every time? by ScentCone · · Score: 0, Offtopic

      When Slashdot makes their code sane, then we can blame the browser.

      Well, what's esepcially funny is that it always renders just fine for me using MSIE. Always. Every time. Heh.

      --
      Don't disappoint your bird dog. Go to the range.
    11. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0
      Otherwise STFU.
      How about Slashdot light? That throwback to 1995 is fucking great, and renders like butter.
    12. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      No I have no problems and I am such a luddite I don't even have a slashdot ID just read articles and sometimes the posts. I should sign up some day but the high ID number would be so humiliating :)

    13. Re:Like, render Slashdot the same way every time? by Silverlancer · · Score: 1

      Mine looks fine also... the comments DONT overlap the navbar...

    14. 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.
    15. Re:Like, render Slashdot the same way every time? by Mozk · · Score: 1

      That's because /. was more than likely designed to work in IE, and IE doesn't render things according to standards.

      --
      No existe.
    16. 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
    17. Re:Like, render Slashdot the same way every time? by allism · · Score: 1

      LC is referring to Proxomitron.

    18. Re:Like, render Slashdot the same way every time? by jd142 · · Score: 1

      I believe its something to do with the timing of the advert iFrames, but I could be completely wrong.

      That must be why I've never seen it. Unless the big slashdot/firefox bug is the little bit of text overlap that occasionally shows up on the left hand menu.

      I am using AdBlock to block http://ads.osdn.com/* so that would also block any iframes that might be screwing up the display even worse.

    19. 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
    20. Re:Like, render Slashdot the same way every time? by Striikerr · · Score: 2, Funny

      As long as the test page includes the "dancing Jebus" from The Simpsons, I'm all for it!

    21. Re:Like, render Slashdot the same way every time? by allism · · Score: 1

      Anyone have any idea why this isn't listed in the Firefox extensions on the Mozilla website? This is incredibly handy...

    22. Re:Like, render Slashdot the same way every time? by DunbarTheInept · · Score: 1

      I keep hearing about this alleged problem firefox allegedly has allegedly rendering slashdot, but I've been using firefox for a couple months now and I don't see it rendering any differently than it did in other browsers (other than the default font choices and the button styles of course).

      What exactly is this alleged problem and how do I see it?

      --

      Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.

    23. Re:Like, render Slashdot the same way every time? by MightyMartian · · Score: 1

      I'm running Firefox 1.0.1 on both Win2k (on two different machines) and Linux. I have yet to see these problems.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    24. Re:Like, render Slashdot the same way every time? by nine-times · · Score: 2
      That being said, I think some sort of Ultimate Browser Agony Test is a good idea.

      Agreed. What's surprising is that this apparently hasn't already been done. Or has it?

      It seems to me that creating such a page should go along with setting the standards in the first place. I mean, when the w3c settles on a standard, don't they create example code and explanations for how things should be rendered? When developers are creating their HTML renderers, don't they test out there renderer against some sort of page that uses tricky examples to make sure it renders properly? Doesn't someone have a page or set of pages lying around already?

      If not, it seems a reasonable suggestion that when the standards are being divised and hashed out that a set of examples are created to illustrate how rendering should happen, if for no other reason then to diminish ambiguity as to what the standard specifies. The same way W3C offers HTML validators, could they offer a browser-standards-compliance validator (even if it wasn't fully automated but required visual verification)? Or is there some reason why that's a bad idea?

    25. Re:Like, render Slashdot the same way every time? by slashkitty · · Score: 1

      It seems like every time for the first visit to the comment area on the site, it's totally messed up. Usually not able to see anything. It would be nice is slashdot gave a damn about firefix users. Even microsoft.com renders better than this!

      --
      -- these are only opinions and they might not be mine.
    26. Re:Like, render Slashdot the same way every time? by hb253 · · Score: 1

      It has always worked perfectly for me as well. I don't know what these other clowns are talking about :-)

      --
      Self awareness - try it!
    27. Re:Like, render Slashdot the same way every time? by bob670 · · Score: 1

      looks fine in IE everytime, but each time I open Slashdot in FF it is a new adventure, and usually take several pages refeshes to get something useful.

    28. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 1, Informative

      When Slashdot makes their code sane, then we can blame the browser.

      No, when Firefox devs admit it's a bug in their code, we can blame the browser. When a valid HTML testcase accompanies the bug report in Bugzilla, we can blame the browser. When nightlies with the bugfix in render Slashdot appropriately, we can blame the browser.

      How many times does this need to be explained to people? Believe it or not, Firefox does have bugs, and your pathological need to point the finger elsewhere is just stupid.

    29. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      It also has _tons_ of unclosed LI tags.

      The end tag for the LI element type is optional. I assume you don't really mean that it has unclosed LI tags, because no browser I've ever tested in can deal with that.

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

    31. Re:Like, render Slashdot the same way every time? by Dolda2000 · · Score: 1
      It also has _tons_ of unclosed LI tags. These obviously can mess up the display quite a lot.
      Actually, HTML (not XHTML, but Slashdot's DTD is HTML 3.2 Final, IIRC) permits this. LI, TR, TD among others work like the P that -- you don't need to close it, it just begins a new paragraph, list item, etc.

      Needless to say, because of that they don't nest.

    32. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      I haven't seen the render problem on /. lately. Maybe it's because /. seems to be taking longer to load recently. Maybe it's due to upgrading to firefox-1.0.1. I dunno.

    33. Re:Like, render Slashdot the same way every time? by Drathos · · Score: 1

      Don't refresh the page when you get the display problem. Cause a reflow. Until I installed SlashFix (which, IIRC, does the same thing), I would bump the font size, then put it back to normal (+, -) after the page had finished loading. This fixed it every time.

      --
      End of line..
    34. Re:Like, render Slashdot the same way every time? by porcupine8 · · Score: 1
      I didn't really mean "quit bitching" - more that I don't seem to be having these problems (and I don't run AdBlock or anything but straight firefox). If, however, I AM having having them but not noticing them, then I do think they must be too small to justify all the bitching. Chances are, though, I'm just not having them.

      I have definitely never seen any overlap like that.

      --
      Warning: Apple/Nintendo fangirl. Likes her electronics cute & cuddly. May be rabid.
    35. Re:Like, render Slashdot the same way every time? by snorklewacker · · Score: 1

      It also has _tons_ of unclosed LI tags.

      The closing tag for LI is optional and always has been. If omitting the closing tag screws up the display, that's the user-agent's fault. TD and TR are now closing -tag optional as well. Of course, TABLE sure as hell ain't -- it won't even render on Netscape 4.x and earlier!

      --
      I am no longer wasting my time with slashdot
    36. Re:Like, render Slashdot the same way every time? by Dysan2k · · Score: 1
      So, shouldn't they use

      and

      rather than without the /?

      --
      -What have you contributed lately?
    37. Re:Like, render Slashdot the same way every time? by bob670 · · Score: 1

      While that is good to know, and I am really not trying to be a PITA about this, why not just use IE? This is why FF is in trouble long term, for the vast majority of users IE is a recognizalbe problem (please note I said recognizable).

    38. Re:Like, render Slashdot the same way every time? by bemenaker · · Score: 2, Interesting

      occasionally, I will get a huge empty black space in the middle of my screen and the text is over it and unreadable, (being black). The white space is far shifted to the right. Or the text is shifted left over the navigation column. Refreshing once or twice clears it up. I get this probably once a week. I use Firefox exclusively.

    39. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      the spec explicity defines behavior for undefined attributes and tags

      Really? Where?

      HTML 4.0 mentions a few guidelines, but they are non-normative, and do not appear in the HTML 3.2 specification as far as I can see.

      It should be a warning that you may be relying on non-standard behavior, but the standard does not prohibit them.

      No, using element types that don't appear in the specification is always a deviation from the specification. You can't just make shit up and call it compliant.

      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.

      The rules are simple. If the element type is defined as to have an optional end tag, you can leave it off. The parser can figure out when an element ends in one of two ways - either the parent element is closed, or an element is opened that cannot be a child of the current element. The HTML 4.01 specification has a handy table that lists which end tags are optional.

      It's why you don't need a close tag for P elements in HTML 3.2, for example.

      You don't need a closing tag for P elements, because it is defined as such in the specification. It's defined in that way, because a smart parser can figure out for itself where P elements close - since P elements can't contain other P elements, the sequence "<p>foo<p>bar" is unambiguously two sibling elements.

    40. Re:Like, render Slashdot the same way every time? by The+Spoonman · · Score: 2, Informative

      Yes, you're the only one. :) In fact, one programmer decided to do something about it: Slashfix. Been using it for a while now and it works just great.

      --
      Which is more painful? Going to work or gouging your eye out with a spoon? Find out!
      http://www.workorspoon.com
    41. Re:Like, render Slashdot the same way every time? by Leffe · · Score: 1

      It's more work writing a browser that parses awful code than it is to write one that supports web standards... why IE, why :'(

    42. Re:Like, render Slashdot the same way every time? by Curtman · · Score: 2, Interesting

      Have you never seen it do this?

      That one isn't anywhere near as bad as the times when the entire page content is shifted one screen width to the right, but it still annoys me very much, and happens almost every time, whereas the page shifting bug only happens I would say 1/20 times as a rough estimate.

      It's not hard to create valid pages that render differently in different browsers. I just want to know why.

      :)

    43. Re:Like, render Slashdot the same way every time? by x136 · · Score: 1

      I've used Firefox/Firebird/Phoenix since version 0.6 or so (and Mozilla before that) through the present, on both OS X and Linux, and I've never seen it either. Good to see I'm not the only one.

      --
      SIGFEH
    44. Re:Like, render Slashdot the same way every time? by HoneyBunchesOfGoats · · Score: 1

      It varies. Here in my apartment, I've only seen that rendering bug once (which is a good record, considering how often I visit /.). When I visited my parents a few weeks ago, it happened every single time on the computer there. Same browser (FF 1.0.1), same OS (Windows XP SP2). Odd behavior.

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

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

    47. Re:Like, render Slashdot the same way every time? by jacksonj04 · · Score: 1

      Because people write awful code.

      --
      How many people can read hex if only you and dead people can read hex?
    48. Re:Like, render Slashdot the same way every time? by Curtman · · Score: 1

      And every time this is mentioned, I begin wondering whatever became of the effort to make Slashdot standards compliant?

      It seemed like a hell of a good idea at the time.

    49. Re:Like, render Slashdot the same way every time? by WWWWolf · · Score: 1

      I have seen this alleged problem happening once, with any firefox version, and I visit Slashdot pretty heavily.

      Though, I've heard this problem appears more if you're on slower connection. I'm always browsing from home-DSL or university...

    50. Re:Like, render Slashdot the same way every time? by aztektum · · Score: 1

      Oddly I have fewer problems with /. rendering in Windows than I do in Mandrake Linux 10.1. My only guess is that it has to do with fonts.

      --
      :: aztek ::
      No sig for you!!
    51. Re:Like, render Slashdot the same way every time? by Curtman · · Score: 1

      I think slashcode ate your tags. Could you repost that with "<"'s in place of the <'s?

    52. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0
      It also has _tons_ of unclosed LI tags.
      That's probably because there is no </LI> tag!
    53. Re:Like, render Slashdot the same way every time? by Curtman · · Score: 1

      Because people write awful code.

      They wouldn't write aweful code, if browsers refused to render aweful code.

    54. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      My firefox renders slashdot the same every time.

    55. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      Probably sounds stupid, but where does it render incorrectly? I can't see any problem with it.

    56. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      I hate not logging in, but I'm using a public workstation.

      I think you have that backwards: horrific html coding like that used by the slashdot maintainers is what will keep IE in widespread use and undermine the efforts of Mozilla, Firefox, and others. Apparently, Microsoft's frequent disregard for W3C recommendations has forced the company to make sure that IE handles all manner of sloppy coding.

      Furthermore, the many demonstrations of slashdot's layout using standard HTML or XHTML and CSS clearly indicate that the conversion is possible and beneficial to users of ALL browsers (yes, even IE).

      sfritsche

    57. Re:Like, render Slashdot the same way every time? by leonmergen · · Score: 1

      Exactly... I've looked all over the page many times before looking for the problem, but I just can't find it!

      Please, can anyone post a screenshot so I can see ? I'm really curious... :-)

      --
      - Leon Mergen
      http://www.solatis.com
    58. 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?
    59. Re:Like, render Slashdot the same way every time? by Night+Goat · · Score: 1

      I've noticed the problem on my home Windows XP box running Firefox, but not on my work computer (running Windows 2000). I also noticed it constantly on the pre-1.0 versions of Firefox running on Ubuntu Linux. Very curious.

    60. Re:Like, render Slashdot the same way every time? by Curtman · · Score: 1

      Unfortunately though most of us have no control over that. Even more unfortunate is that even more of us don't care one way or the other as long as it looks right. Microsoft is the only one that is really in a position to improve the situation, but it is in their best interest not to correct this, because it reinforces the 'pages don't render correctly in other browsers' misconception.

    61. Re:Like, render Slashdot the same way every time? by Suddenly_Dead · · Score: 1

      I saw a problem a couple times on "Phoenix" 0.4 or 0.3, I think. Since then Firefox has rendered the site perfectly fine. It looks identical to what IE and Opera give me, every time.

      Perhaps the people's ISPs are dropping packets or something?

    62. Re:Like, render Slashdot the same way every time? by johansalk · · Score: 1

      I second that. I've used Mozilla ever since they had those M13 and before version numbers, mozilla phoenix (firebird/firefox) ever since it was 0.1, and I never had any problems with rendering slashdot.

    63. Re:Like, render Slashdot the same way every time? by plover · · Score: 1
      why not just use IE?

      If we "give up" and switch to IE because it works, then we've literally given up hope on having standards independent from Microsoft.

      The other reason is that as developers we should be used to eating our own dogfood. Or put another way, if people stop bitching about the formatting, it will never get fixed. Not that a year of bitching has gotten it fixed yet, but without the pressure there will never be incentive to fix it.

      --
      John
    64. Re:Like, render Slashdot the same way every time? by damiam · · Score: 1
      While that is good to know, and I am really not trying to be a PITA about this, why not just use IE?

      Because installing a or even reflowing every page is much less cumbersome than using a browser that doesn't support gestures or tabs.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    65. Re:Like, render Slashdot the same way every time? by stevey · · Score: 1

      Retooling Slashdot with CSS has been done already, but it didn't get integrated with the site.

      The slashcode system generates the output pages that we see via the use of template files - to change the output we see there would need to be lots of template tweaking, and cleanups.

      In short CSS for /. is harder than changing a single HTML page, because of the nature of the site.

      Still it'd be worth it in terms of bandwidth savings, and letting the site work well into the future.

    66. Re:Like, render Slashdot the same way every time? by damiam · · Score: 1

      Oops. That should be "installing a simple extension".

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    67. Re:Like, render Slashdot the same way every time? by aichpvee · · Score: 1

      What version are you using? I never saw it until I upgrade to 1.0 and after that it happened relatively often.

      --
      The Farewell Tour II
    68. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0
      From http://www.w3.org/TR/REC-html32.html:
      <!ELEMENT P - O (%text)*>
      P's end tag is optional.
      <!ELEMENT table - - (caption?, tr+)>
      TABLE's end tag is mandatory.
      LI, TR, TH, TD also have optional end tags.
    69. Re:Like, render Slashdot the same way every time? by Curtman · · Score: 1

      "That means it's illegal for them to do shit like engineered lack of interoperability. "

      Why would Microsoft count itself as a member of the w3c if it has no desire to follow the standards which it puts forth?

      Unless it has a goal of engineered lack of interoperability like you say, it really makes no sense.

    70. Re:Like, render Slashdot the same way every time? by porcupine8 · · Score: 1

      Woah, no, nothing even close to that. Honestly, it always looks perfectly normal.

      --
      Warning: Apple/Nintendo fangirl. Likes her electronics cute & cuddly. May be rabid.
    71. Re:Like, render Slashdot the same way every time? by porcupine8 · · Score: 1

      I originally had 1.0, I *think* I upgraded to 1.0.1 when it came out.

      --
      Warning: Apple/Nintendo fangirl. Likes her electronics cute & cuddly. May be rabid.
    72. Re:Like, render Slashdot the same way every time? by MNJavaGuy · · Score: 1

      You aren't alone. I've never noticed a single issue rendering Slashdot and I've been using Firefox for several versions. I just loaded it up in IE and, aside from a few font settings I changed in FF, it looks as identical as could be expected. YMMV, I guess.

    73. Re:Like, render Slashdot the same way every time? by Curtman · · Score: 1

      Just out of curiosity, does Safari respect the top margin on the 2nd of the two div's on my second link (In other words, is there space between the bottom of the first image and the top of the second div? I imagine it behaves like Konqueror right?

    74. Re:Like, render Slashdot the same way every time? by porcupine8 · · Score: 1

      Hm, no, the first image is sitting right on top of the second black band. But then, I'm also using Safari 1.0.something b/c I only have OS X 10.2.8.

      --
      Warning: Apple/Nintendo fangirl. Likes her electronics cute & cuddly. May be rabid.
    75. Re:Like, render Slashdot the same way every time? by Nailer · · Score: 1

      Slashdot declares HTML version 3.2, and the w3c validator is actually much stricter than the written standard.

      Sure. But do you think the written standard mentions you need to close a table or not?

    76. Re:Like, render Slashdot the same way every time? by Curtman · · Score: 1

      I wonder then, do some browsers count the margin from the end of the div which doesn't expand, and some count it from img which hangs out of it?

      Its just something I noticed a long time ago, and I've never been able to explain.

    77. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      You're timeframe is way off. Slashdot was designed for Netscape 3/4. You think a Linux fanboy site designed for IE?

    78. Re:Like, render Slashdot the same way every time? by Fjornir · · Score: 1
      ctrl-plus then ctrl-minus.

      But given how badly slashcode html fails to validate it's not too surprising that firefox has trouble with it.

      --
      I want a new world. I think this one is broken.
    79. Re:Like, render Slashdot the same way every time? by c4ffeine · · Score: 1

      Well, there's me. I've never seen anything wrong with slashdot on firefox. I've heard that the problem is fairly noticeable, so you'd probably know if it came up. What is it, anyways?

      While we're on problems I haven't seen before, what is up with the comments about "nothing to see here, move along" or something like that?

      --
      "73% of quotes on the Internet are made up" -Ben Franklin
    80. Re:Like, render Slashdot the same way every time? by allism · · Score: 1

      the little bit of text overlap that occasionally shows up on the left hand menu.

      yep, that's it.

    81. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      If he's too stupid to use "Preview", don't expect him to have the mental capacity to be able to use &lt;.

      Also, it's "&lt;"s (or &lt;s) and "<"s (or <s), not "&lt;"'s and "<"'s (or <'s).

    82. Re:Like, render Slashdot the same way every time? by GraemeDonaldson · · Score: 1

      Probably because it's not so much an extension as a hack to work around a bug that appears on a single (?) site, and even then only for some people/some of the time. FF extensions are supposed to provide additional functionality, not fix bugs. If you can make use of the power of extensions, more power to you, but don't expect mozdev to care much.

      --
      I think, therefore I am. I think?
    83. Re:Like, render Slashdot the same way every time? by Curtman · · Score: 1

      "Also, it's"...

      Not this time.

    84. Re:Like, render Slashdot the same way every time? by caluml · · Score: 1

      It's probably because you're on a very fast connection, and the whole pages hits your browser before it renders.

    85. Re:Like, render Slashdot the same way every time? by Anonymous Coward · · Score: 0

      || Am I the only person who has never had any issues with slashdot and firefox? ||

      Yes! Yes, you are. For the rest of us, /. is NTFS (Never The Fucking Same).

    86. Re:Like, render Slashdot the same way every time? by Bam359 · · Score: 1
      I think he ment: So, shouldn't they use

      and

    87. rather than without the /?
  • Re:Like, render Slashdot the same way every time? by Elwood+P+Dowd · · Score: 1

    Or AdBlock might cause a reflow after the page is loaded. That's how everyone else solves the problem.

    --

    There are no trails. There are no trees out here.
  • Re:Like, render Slashdot the same way every time? by shaitand · · Score: 1

    Ever load the frontpage and there is no content except the sidebar? That's where. It happens about once every 20 page loads.

  • Re:Like, render Slashdot the same way every time? by Eric+Savage · · Score: 1

    Bandwidth is dirt cheap these days. Using the stats from A List Apart, they would save 14GB a day, which they claim would save $3650/year, or about 5% of a decent developer's salary. Now if you use a realistic bandwidth cost, since slashdot isn't running on some $5/month hosting account, you are looking at a savings of $3-400/year, or one day of that developer's time, which is a lot less time than it would take to retool the whole site.

    I think it would be smart for them to do it, but not for strictly-bottom-line reasons.

    --

    This is not the greatest sig in the world, this is just a tribute.
  • Re:Like, render Slashdot the same way every time? by Bander · · Score: 1

    I wonder if the same effect could be implemented in Greasemonkey? There are already a couple of /. specific scripts in there, and I get tired of having to restart FF every time I add an extension.

  • Re:Like, render Slashdot the same way every time? by canuck57 · · Score: 1
    Line 2007, column 7: end tag for "TABLE" omitted, but its declaration does not permit this

    Likely the table error should be fixed but I have found validator.w3.org to be of an "interesting site" only. What counts is that most browsers present it properly. The rest is hyperbole and perhaps some chit chat value.

    LI tags do not need to be closed, it is just the author of the validator thinks so. Either that or maybe a new spec changes that but I admit, I don't read evey one that was ever written.

    And what if the output was written to a prior version? Validator will surely complain. Try re-writing the internet because someone decided to change the spec in the last version.

    What would be nice if the tool relaxed a bit and worked on pointing out issues with the top 3-5 browsers in presentation. The world does NOT revolve around w3.org.

  • Re:Like, render Slashdot the same way every time? by aichpvee · · Score: 1

    Help->About Mozilla Firefox

    --
    The Farewell Tour II
  • Re:Like, render Slashdot the same way every time? by porcupine8 · · Score: 1
    (At the time I wrote that, I was at home using Safari. Which I also am right now, and thus still can't check.)

    (Just so you don't think I'm too dumb.)

    --
    Warning: Apple/Nintendo fangirl. Likes her electronics cute & cuddly. May be rabid.
  • Re:Like, render Slashdot the same way every time? by Reality_X · · Score: 1

    It's funny you should mention that.

    I *never* saw the slashdot problem in Firefox up until recently, when I blew away my Firefox installation (on Windows) and did a fresh install of 1.0.1.

    Even then, I only see the issue when logged in.

  • Re:Like, render Slashdot the same way every time? by say · · Score: 1

    Uh, the validator quite easily identifies it as HTML3.2 and validates against that specification. Newer specs require LIs to be closed. Older don't.

    --
    Roses are #FF0000, violets are #0000FF, all my base are belong to you
  • Re:Like, render Slashdot the same way every time? by andreyw · · Score: 1

    Text becomes shifted all the way right/left, making it impossible to read. Change font size (ctll-mousewheel) fixes it.

  • Re:Like, render Slashdot the same way every time? by Dysan2k · · Score: 1

    Yes I did, thank you. (I really should go look at my post history and pay attention.. sorry about that.)

    With <p> and <li> were in reference to using the break tag for HTML 4 and XHTML compliancy. (<br /> rather than just <br>. Shouldn't they all be the same?

    --
    -What have you contributed lately?
  • 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 Anonymous Coward · · Score: 0

      Opera may not be perfect, but IE shouldn't even be labeled a browser due to its lack of adherance to web standards. Is a car with a shower door for a windshield really a car? Yes, I suppose, but pretty useless.

    2. Re:Why just microsoft? by bcmm · · Score: 2, Funny

      Yeah.
      I mean, my opinion would be that the browser should, like, make pages look really cool, even if they are really badly made, and do, like, lots of cool stuff.

      Why can't they do what I want? I mean, I made a web page, and it looks crap in all the browser I've tried.

      --
      # cat /dev/mem | strings | grep -i llama
      Damn, my RAM is full of llamas.
    3. 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.

    4. Re:Why just microsoft? by myukew · · Score: 1

      Not being perfect is no reason for not asking for test which measure improvements.

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

    6. Re:Why just microsoft? by gardyloo · · Score: 1

      the browser should, like, make pages look really cool, even if they are really badly made

      That's called the /. color test.

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

    9. Re:Why just microsoft? by NanoGator · · Score: 1

      "Has anyone (even Opera) managed to create a browser that does what all the web designers want it to do?"

      I can't answer your question but I can tell you that it is very seldom that I have to fire up another browser because Opera isn't rendering properly.

      Normally I wouldn't bring it up, but I seriously doubt the sites I visit even consider testing with Opera.

      --
      "Derp de derp."
    10. Re:Why just microsoft? by Jicksta · · Score: 1

      W3C already is the de facto standard and has been for about half a decade.

      The chimpanzees at Microsoft didn't just sit down together and say, "Okay, let's make a font tag! It can handle stuff like size, face, and even color!"

      Their aim, I'm sure, was to model IE's rendering engine on the W3C standards, but like chimpanzees, no matter what they did, they just couldn't get that triangular block through that circular hole.

    11. Re:Why just microsoft? by Mozk · · Score: 1

      That's because they are not informed or misinformed about what is right. Microsoft is ruining the Internet because of IE. We need to explain to users what is right and wrong, so we can fix it, so everything can be better, and we can all be happy.

      --
      No existe.
    12. Re:Why just microsoft? by Anonymous Coward · · Score: 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

      No, no, no! I've seen people whining about the box model in Internet Explorer for years. Microsoft fixed it in 2001, when they released Internet Explorer 6.0.

      They maintain backwards compatibility with 5.x by using "quirks mode", but pages that comply with the W3C specifications very rarely trigger that, and it's easily fixed.

      Occasionally, dumb people say that their "compliant" pages trigger quirks mode because of the XML declaration, to which I say "stop talking about specifications you haven't read", pages that include XML declarations cannot be transmitted as text/html, and so you shouldn't be transmitting them to Internet Explorer in the first place.

    13. Re:Why just microsoft? by jejones · · Score: 1

      In this regard, I have an itch that I hope to one day scratch.

      To be honest, I can't do either of the two things that I ought to be able to do:

      1. Given a hunk of HTML/CSS, know without feeding it to a browser what is right.

      2. Given something I want to look a certain way, know what HTML/CSS is needed to get what I want.

      What someone needs to write is an expert system that renders HTML, so that you can ask it questions: "Why does X overlap Y?" and get answers in terms of the standard: "Because X and Y [whatever the reason is]...(see the Blah standard, section X.Y.Z, and the Mumble standard, section P.Q.R)."

      Even if I fail to produce the program, I ought to learn HTML and CSS in the process of trying to write it, right?

    14. Re:Why just microsoft? by Anonymous Coward · · Score: 0

      No, Netscape did it too.
      I don't remember which, but either frames or tables are because Netscape implemented a non-standard "feature", which everyone else just supported because the dominant browser did.

    15. Re:Why just microsoft? by Pionar · · Score: 1

      If you look through the CSS and XHTML specs on the W3C site, you'll find the answers to this. They tell you how a user agent (browser) is supposed to behave.

    16. Re:Why just microsoft? by Anonymous Coward · · Score: 0

      W3C already is the de facto standard and has been for about half a decade.

      Although HTML is an ISO standard (ISO15545), when it comes to XML, they're the de jure standard as well. Which is kind of funny given that a number of ISO standard formats are in fact based on XML.

    17. Re:Why just microsoft? by MikeFM · · Score: 1

      I think the text of the article made it clear that such acid tests are a goal for all browsers to reach. IE is just the biggest competior with the worst support.

      It'd be good to see all popular browsers pass such tests on CSS2. CSS3 should already be in the works to test against.

      Opera's CSS2 support seems better than IE's but not quite on par with Firefox. Safari has some weird quirks now and then but overall isn't much worse than Opera.

      --
      At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
    18. Re:Why just microsoft? by mr.newt · · Score: 1

      It's not that IE has some other standard that people could just conform to. It has bugs that make it unpredictable and do not operate by the published standards.

    19. Re:Why just microsoft? by Anonymous Coward · · Score: 0

      You've never heard of the tag? That alone eliminates any sense of sympathy I have for Netscape and it's inability to function as a going concern. How about jwz putting in special code to change the throbber when you visited his webpage? Fucking stupid. If it weren't for AOL, he'd be where he belongs: poor.

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

    21. Re:Why just microsoft? by Pionar · · Score: 1

      True, but people are still using 5.5. My workplace didn't dump 5.5 until this year, when they switched to XP from 2000.

    22. Re:Why just microsoft? by 0xG · · Score: 1

      Why just "web designers"?

      If it was just up to "web designers", every page would use copious amounts of ActiveX, Java scripts, and enough cookies to feed a pack of cub-scouts:
      Screw security!
      Cornhole privacy!

      No, how about a contest for "web designers" to design a webpage without gratuitous use of Java Script, ActiveX or cookies? It is quite possible, but most "web designers" are just lazy...

      --
      A pox on web designers who feel that window.innerWidth == screen.availWidth
    23. Re:Why just microsoft? by mikis · · Score: 1

      I can't answer your question but I can tell you that it is very seldom that I have to fire up another browser because Opera isn't rendering properly.

      As a paying Opera user, I'm sorry to say that I almost completely switched to Firefox, mainly because of problems with:

      1) GMail
      2) Yahoo! Mail / My Yahoo!
      3) Each and every wysiwyg HTML editor component (HTMLarea, TinyMCE...)

    24. Re:Why just microsoft? by Anonymous Coward · · Score: 0

      What do you expect Microsoft to do, travel back in time to fix 5.5? Internet Explorer 6.0 has been listed as a critical upgrade in Windows Update for well over a year, Microsoft have done pretty much everything they can to fix the box model problem and get people to upgrade.

    25. Re:Why just microsoft? by ChatHuant · · Score: 1

      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.

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

      That's really funny, because history tells us exactly the opposite. Either you're too young and don't know your history, or you're intentionally spreading FUD. Please read about Netscape and tags like blink, spacer, multicol, center, keygen and others, for example here or, to see how the problem was regarded at the time, here.

      So, do you think you may be a knee-jerk "Microsoft sucks!" person after all ?

    26. Re:Why just microsoft? by Reene · · Score: 1

      This should go without saying, but not all "web designers" are incompetent hacks. Some of us actually look at web design as an artform. The challenge of getting a web page not only working but looking downright good in every browser you throw it at is quite exhilirating. This is not just for designing personal sites but sites for businesses as well.

      It's unfortunate that there are people that believe that using things like ActiveX is not only "nifty" but absoloutely necessary for every website you could think about designing. Arguing with these people gives me headaches. I just chock it up to horrendous teaching and block it out now.

      --
      "He does look a bit Oompa like, even if his Loompa is a bit off-kilter."
    27. Re:Why just microsoft? by MoneyT · · Score: 1

      And just how pray tell do you explain to a user that the fact that their browser (which renders their favorite porn page correctly) is infact broken because it doesn't render something which adheres to different standards correctly. Remember, as far as the user is concerned if it does what they want it to do correctly (FROM THEIR STANDPOINT) then it's right. It doesn't matter how many coding faux pas it makes behind the scenes.

      --
      T Money
      World Domination with a plastic spoon since 1984
    28. Re:Why just microsoft? by jp10558 · · Score: 1

      You know, 3 I get, but I'd be damned if I would let 1 or 2 drive me from my browser. I mean, look - they are competitors in a wide open market of web mail providers which don't work with my browser of choice. I personally find it much easier to type in a different URL in the address bar compared to getting a whole new browser set up and working the way I want (assuming that is possible).

      Of course, as I've stated before on /. I strongly believe that e-mail ought to have nothing to do with a webpage.

      --
      Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
    29. Re:Why just microsoft? by Anonymous Coward · · Score: 0

      Your workplace is filled with dumbshits. IE5.5 has been unpatched for years and is game for every security hole since.

    30. Re:Why just microsoft? by Anonymous Coward · · Score: 0

      Funny how many of those evil Microsoft extensions are now being incorporated into FireFox, Opera, and Safari.

      Maybe they DELIBERATLY extended things to solve real world problems while the standards committees DELIBERATLY sat around jawjacking. Just a thought, hater.

    31. Re:Why just microsoft? by Skrybe · · Score: 1

      Exactly! Some of the standards make sense to some people but not to others. Frankly I find some of the standards very counter-intuitive -sizing and spacing ones particularly.

      That said, it'd be nice if everyone who builds a browser would play along with the standards rather than interpreting them as they see fit. At least then we could assume our code would look the same in any browser. I must say though that it's getting much closer than it was about 2 years ago.

      Initially I thought browser dependant HTML/CSS extensions were a good idea. eg: If something isn't mentioned in a standard then it's fine if MS implement it however they like. I'm leaning away from that now though, because it means we wind up in the same messy situation where every browser renders pages differently. Now I think the best thing to do would be to hold back features until they can be officially added to the standard. As a corollary the standard needs to be updated more swiftly :)

    32. Re:Why just microsoft? by MoneyT · · Score: 1

      Heh, even complying with standards docs have their issues, and sometimes interpretation is because things aren't clear:

      http://weblogs.mozillazine.org/hyatt/archives/20 05 _01.html

      --
      T Money
      World Domination with a plastic spoon since 1984
    33. Re:Why just microsoft? by CaptCovert · · Score: 1

      That said, it'd be nice if everyone who builds a browser would play along with the standards rather than interpreting them as they see fit.

      While that's a good idea, in theory, it loses out on one major factor: Money. Whenever a browser can't render something, or renders it to standards and it doesn't look as 'pretty', it loses money. This was a major impetus for the 'quirks mode' found in IE6, as well as backwards compatibility.

      User-Agent designers have to keep in mind that not every web designer is a guru (This is the IT world folks, everyone thinks everyone else is a complete idiot), and as such tends to try to 'interpret' code as best they can. The problem here is: it never ends up the same way twice. The nature of the beast when it comes to competition.

      Of course we could all just use IE, and let MS set the standard. Then everything would be the same and always work (Who cares about Linux users anyway? Cheap Bastards).

    34. Re:Why just microsoft? by femtoguy · · Score: 1

      I mean, that's do question. Do people want fire that can be fit nasally?

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

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

    1. Re:"acid" by CrankyFool · · Score: 1

      But not when talking about the way RDBMS do transactions :)

    2. Re:"acid" by stupidfoo · · Score: 0

      Never acid again.

    3. Re:"acid" by ArsonSmith · · Score: 1

      But you can't put acid into just any test without doing some harm

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    4. Re:"acid" by Geoffreyerffoeg · · Score: 1

      I tried that in chemistry class, and someone (you know how Murphy's Law works) pulled out the sodium hydroxide by mistake....

  • Opera by stupidfoo · · Score: 0, Troll

    This is laughable. Opera is hardly the bastion of interoperability.

    1. Re:Opera by Anonymous Coward · · Score: 0

      Hardly. If I'm not mistaken, Macromedia Dreamweaver and Adobe Go!Live both use Opera's Presto Web Rendering Engine. Those both produce very W3C compliant code.

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

    3. 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?).

    4. Re:Opera by loralora · · Score: 1

      Totally. I use Opera, but this is just a PR gimmick isn't it?

    5. 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
    6. Re:Opera by Taladar · · Score: 1

      Actually I use Opera since IE4 times and in all that time I didn't find more than half a dozen Websites that did not work in Opera.

    7. Re:Opera by Freexe · · Score: 1
      You either don;t go to many websites or you are lying.

      I've used Opera since v4 (Jun 2000) and back then things weren't pretty, IE4 was Oct 1997 (same time as Opera 3.5) which was even worse.

      --
      "In a time of universal deceit - telling the truth is a revolutionary act." - George Orwell
    8. Re:Opera by scoobrs · · Score: 1

      That's funny. I paid that for Opera a few years ago rather than use Firefox for free and came out ahead.

      --
      -Those who would give up essential liberty to purchase temporary safety deserve neither. -Ben Franklin
    9. Re:Opera by Anonymous Coward · · Score: 0

      What does that have to do with anything?

    10. Re:Opera by Anonymous Coward · · Score: 0

      Unlike bloatfox, Opera works on low-end computers. I should know, I'm stuck on one at work right now.

    11. Re:Opera by Anonymous Coward · · Score: 0

      > what's next, a $40 terminal emulator?

      You'd be amazed how many businesses will purchase SecureCRT instead of simply using PuTTY. It's not even as functional.

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

      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.

      Actually, you're combining two different concepts: Firefox is standards compliant; with Opera you just get the standard complaints.

    13. Re:Opera by stupidfoo · · Score: 1

      SecureCRT not as functional as PuTTY? You must think that terminal software is only good for connecting via telnet and SSH.

      How good does PuTTY do at serial connections and WYSE emulation? How about VT100? How about dialer support? When I've got data coming in over RS485 or RS232 how exactly does PuTTY handle that?

      PuTTY is a nice free tool, but it doesn't do 1/100th of what CRT/SecureCRT can do. Not even close.

    14. Re:Opera by Anonymous Coward · · Score: 0

      What I like about Opera for my users is that it Mostly Just Works, people actually LIKE the google ads, and it comes with a mail application that gives me the perfect excuse to make people get rid of Outlook. Plus it has a small disk/memory footprint.

    15. Re:Opera by Taladar · · Score: 1

      I meant IE 4 was the last version of IE I used not that I used Opera since the release of IE4

    16. Re:Opera by scoobrs · · Score: 1
      I'm feeding the troll here, but #1 why not? and #2 damn right. Opera does one thing and does it well. Firefox is mostly buzz these days as most of the features aren't user-friendly, swift, or light on memory. So long as IE continues to be ignored or held back, the market is wide open for innovators.

      Why does Open Source have to beat competitors who fill a niche and really try to do their jobs well? Do we have to release a faster, lighter, Minimo (Moperilla?) browser simply because commercial competitors are evil or is it because of the spirit of advancing the art? It's fine to admit that the competition is better at something and in fact, it's required in order to improve. Why not admit that the Firefox interface is still pretty ugly?

      --
      -Those who would give up essential liberty to purchase temporary safety deserve neither. -Ben Franklin
    17. Re:Opera by QuietLagoon · · Score: 1
      I'm feeding the troll here, but #1 why not? and #2 damn right. Opera does one thing and does it well. Firefox is mostly buzz these days as most of the features aren't user-friendly, swift, or light on memory.

      I'm not sure why you thought my message was a troll, it was intended as such. Indeed, if you could see my user agent string, you'd see that I use Opera (currently 8.0b2, build 7483).

      I thought my comment was a simple accurate observation, not a troll.

    18. Re:Opera by AK+Marc · · Score: 1

      I go to a large number of web sites. The only ones I find that don't work are some secure sites, and some that use Java. I keep IE for running Cisco Secure ACS, the local trouble ticket system (which sucks and is being replaced soon) and my bank site (which works fine with Opera, but they decided to block Opera because they think it is more secure to require IE). The number of sites that IE can't display correctly is much higher. That's the reason I had to load a second browser in the first place, but it ended up that everything I tried was much better than IE...

    19. Re:Opera by QuietLagoon · · Score: 1
      I'm not sure why you thought my message was a troll, it was intended as such.

      It was not intended as such. (sometimes I wonder why I miss those egregious typos when I proofread my comments.....)

    20. Re:Opera by eugene+ts+wong · · Score: 1

      I paid as well. The time that I save has definitely earned me more than $40. I still have the ad banner up there to bring in revenue for them. It doesn't take up that much space.

      Paying for quality software is always better than using bad free software. Congratulations for seeing the wisdom Opera.

    21. Re:Opera by canuck57 · · Score: 1
      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.

      It might be more correct to say, Microsoft's lack of standards has led it to the same predicament as any other mature off the cuff systems, you can't change it without breaking it until you understand it completely. And not even M$ with 40B in the bank can do it.

      Best ot stick to published and accepted standards not brought on by business, but by those without a dollar bill in mind.

      Going to stick with Mozilla and Firefox.

  • IE not worth caring about by DigitalTechnic · · Score: 0

    Is anybody actually caring about IE at this point? There's only so much you can put up with before it's time to cement its feet and dump it in in the ocean.

    1. Re:IE not worth caring about by thegnu · · Score: 2, Informative

      I think the number of people who care about IE are just under 90% of the browser market, and anyone who might fix their computer (another 6-7%).

      So maybe a few people.

      --
      Please stop stalking me, bro.
    2. 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?

    3. Re:IE not worth caring about by data1 · · Score: 1

      Yes, Plenty of people care what happens to IE.
      Many organizations have IE as the standard and build internal applications that work with no other Browser. Re-engineering and re-implementing these systems would be a costly and probably lengthy process.
      That would simply not fly since most people are of the min "If it ain't broke, why fix it?"

    4. Re:IE not worth caring about by shawn(at)fsu · · Score: 1

      Yeah well when you client says it has to work with IE x and up you don't have much choice.

      --
      500 dollar reward for tip(s) leading to the arrest of the person(s) who stole my sig.
    5. Re:IE not worth caring about by Doctor+O · · Score: 2, Interesting

      This is not +4, Insightful, because the OP is correct. Amongst others, I work for BBDO, TBWA, Publicis and RSCG, and none of those care much for IE, because if you have designers who understand the medium, it's easy to build nice (==compliant) XHTML/CSS which renders just fine everywhere. Most problems derive from graphics-laden sites sketched up in Photoshop (or even worse, XPress or Freehand) by aging print designers which require nonsensical pixel-perfect rendering and are demanded to be built "exactly like the layout!". Broken design, broken result.

      I might add that of course there are many huge players in the field who still travel the 'optimized for IE' road and build shitty stuff which just renders in one or two versions of IE (rendering of CSS changed severely in some areas between IE 5.0, 5.5 and 6.0). But those who understand what they do, produce good quality. The IE only pages are already disappearing, and actually my perspective on this is not that it happens because every new IE release introduces more incompatibilities with old versions and people are fed up with kludging up their HTML when they can just rebuild it and have it work everywhere in half the time which is required for debugging all those stupid side effects. Look at Google Maps as an example. Doesn't look very 'optimized for IE' to me.

      (I only talk about professional web design. I refuse to discuss the HTML practices of hobbyists, they'll build broken pages until browsers refuse to display them completely (won't happen), and frankly shouldn't be bothered with such discussions. Let them play with it, maybe some of them get enough out of it to learn how to do it the right way later.)

      --
      Who is General Failure and why is he reading my hard disk?
    6. Re:IE not worth caring about by Doctor+O · · Score: 1

      Aw, shit. Preview, preview, preview.

      I meant to write:

      The IE only pages are already disappearing, and actually my perspective on this is not that it happens because of Moz/FF, but because every new IE release introduces more incompatibilities with old versions and people are fed up with kludging up their HTML when they can just rebuild it and have it work everywhere in half the time which is required for debugging all those stupid side effects.

      --
      Who is General Failure and why is he reading my hard disk?
    7. Re:IE not worth caring about by stupidfoo · · Score: 1

      The OP said that no one should care about IE anymore. Not that no one should be crafting IE only pages/sites anymore or creating sites that are "optimized for IE".

      And no one really cares who you do work for.

    8. Re:IE not worth caring about by waveclaw · · Score: 1

      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?

      According to my Apache logs (you do read your logs, dont you?), 90% of my 'IE' users are interested in some page called /scripts/..%5c%5c.. that my Linux boxes don't have. The remaining 10% of the 'IE' users are just interested in my music and artwork (mostly mp3s and jpg's.) But 90% of my total users seem to be search bots like googlebot.

      Got any recomendations on improving that 90% now?
      --

      "You cannot have a General Will unless you have shared experiences. You cannot be fair to people you don't know."
    9. Re:IE not worth caring about by Doctor+O · · Score: 1

      Read my post again. It's exactly what I said. The OP is correct, no one cares for IE. It's being tested against, but no longer being coded for. What was your point again?

      And FWIW, in this context it's well relevant whom I work for, because those make up a significant part of market share in building web sites (at least in Europe, don't know or care about the US), which means my observations are pretty representative of the market.

      --
      Who is General Failure and why is he reading my hard disk?
  • Oddly enough by Inverse+Icarus · · Score: 1

    Oddly enough, when I went to "read more", FireFox spat this at me:

    404 File Not Found
    The requested URL (articles/05/03/16/1556228.shtml?tid=109) was not found.

    If you feel like it, mail the url, and where ya came from to pater@slashdot.org.

    Looks like the bar has already been set too high!

  • Opera? by Anonymous Coward · · Score: 0

    Not even THEY get their browser download under 2 megabytes anymore.

    And thusly, fail it.

    1. Re:Opera? by bhtooefr · · Score: 1

      They're under 4, with all features except voice (they've been holding at 3.5-3.6, actually, since the 6.0 days, IIRC). Firefox is at 4.5, last I checked, with much less features than Opera.

  • make microsoft accountable by Anonymous Coward · · Score: 0

    yeah, I'm sure they'll agree to that!

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

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

  • I LOVE this ERA! by Anonymous Coward · · Score: 0

    Name me any other big industry where the little guy can still try to put the smack down on the big one!

  • 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
    2. Re:Implementing full standards would help by bhtooefr · · Score: 2, Informative
      Opera 8.0B3 fails the following on HTML4:

      6_16-BF-01 Frame Target Names (part C/D/F
      Verify that the user agent ignores target names that do not start with an alphabetical character (a-z, A-Z)
      Test for assertion 6.16-1

      This is 6_16-BF-01c.html

      When you click on this link, 6_16-BF-01f.html should load in THIS WINDOW, NOT in the window where 6_16-BF-01d.html is now. According to the spec, user agents must ignore target names that do not begin with an alphabetic character.
      (puts it in the D window)

      7_4_2-BF-02 The TITLE element (fails miserably - but does any browser actually PASS that one?)

      11_2_6-BF-02 Table cells: The TH and TD elements (on columns, colspan = 0 is set to 1, not all)

      13_3-BF-01 Generic inclusion: the OBJECT element (no image displays)

      13_3_1-BF-01 Rules for rendering objects (renders the object anyway, even though it shouldn't be able to)

      13_5-BF-01 Notes on embedded documents (text didn't show)

      13_6_1-BF-02 Client-side image maps: the MAP and AREA elements (fails - some parts are clickable)

      16_2_2-BF-02 The FRAME Element (fails - cells are not vertically resizable if in the same row as nonresizable cells, even if noresize isn't set)
    3. Re:Implementing full standards would help by bhtooefr · · Score: 1

      (Sorry, clicked Submit)

      16_2_2-BF-03 The FRAME element (depends - no scrollbars are shown on scrolling="no", but wheel still scrolls it)

      18_2_1-BF-02 The SCRIPT element (fails)

      18_2_3-BF-14 Intrinsic events (fails)

      Whew...

      However, there is no CSS test suite, or a JavaScript test suite (some JavaScript is tested in this, but not much).

    4. Re:Implementing full standards would help by NanoGator · · Score: 1

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

      It'd also be nice if the standards developed by said committe weren't ambiguous to the point that every fricken browser ever made didn't violate them.

      --
      "Derp de derp."
    5. Re:Implementing full standards would help by kwerle · · Score: 1

      That sounded great! Thought I'd take a look...

      Many (50% or more) of the rules I looked at (not many) ended with the line

      Tests: None

      I didn't look at that many, so maybe I was just unlucky, but it didn't seem like a good sign.

    6. Re:Implementing full standards would help by northcat · · Score: 1

      There is also some CSS testing.

    7. Re:Implementing full standards would help by untouchable · · Score: 1

      Why was this modded up? Is the poster trying to prove Opera 8.0B3 (The B stands for 'Beta') isn't compliant? What was the point?

      --
      As Seen On TV's? Come back!!!
    8. Re:Implementing full standards would help by bill_kress · · Score: 1

      And reference browsers that web pages could be checked against!

    9. Re:Implementing full standards would help by Curtman · · Score: 1

      Is the poster trying to prove Opera 8.0B3 (The B stands for 'Beta') isn't compliant?

      I think that's very much the point. Otherwise known as the pot calling the kettle black.

    10. Re:Implementing full standards would help by Elminst · · Score: 1

      Firefox 1.0.1 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1) also FAILS all of the same tests that the parent poster lists..

      So I guess Firefox is not compliant either...
      Perhaps the mozilla coders should take the Acid test themselves...

      --
      No unauthorized use. Trespassers will be shot. Survivors will be shot again.
    11. Re:Implementing full standards would help by XO · · Score: 1

      wtf? Must IGNORE a target with a non-numeric character to start?

      Did they forget that the proper way to target a new window is "_BLANK" (or is it _NEW ... I can never remember, I don't do markup that often)??

      Or are they trying to undo people targetting new windows?

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  • 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 Rylz · · Score: 1

      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?

      A standards compliant IE would do more to help web designers do what they do best without worrying about how it's going to render on the browser that 90% of the world uses than it would to help MS.

      --
      Sometimes you've gotta roll the hard six.
    4. Re:Why Bother? by Anonymous Coward · · Score: 0

      If microsoft simply adds tabbed browsing the majority of users will not bother to download and install firefox when windows will make them install ie7. Internet Explorer will always remain the standard browser for computers running windows whether it is inferior or not.

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

    6. Re:Why Bother? by TheGavster · · Score: 1

      This wouldn't be taking initiative. If the alternate browsers all say 'we support the standard HTML test page', then IE will follow suit, just as it did with popup blocking, and now supposedly in IE7, tabs.

      --
      "Because Science" is one step from "Because old book". Try "Because of my experiment testing my falsifiable assertion".
    7. Re:Why Bother? by ReverendLoki · · Score: 1
      The only reason I keep IE around instead of using Firefox for everything is that, for various reasons, there are 3 or 4 pages that I use that MUST use IE to render properly. Because of those IE oddities and the fact that it's the most popular browser, web designers must code for IE, and when forced to choose between user their time to make a site IE compliant or standards compliant, that designer makes te site IE compliant if they don't want to lose their job most of the time. If IE was standards compliant, this would not be an issue - and I wouldn't have to use IE at all.

      Of course, that may be Microsoft's biggest reason NOT to make IE standards compliant...

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    8. Re:Why Bother? by northcat · · Score: 1

      If all webmasters don't code for IE and put a message that says this page wont look good in IE, people will switch.

    9. Re:Why Bother? by Anonymous Coward · · Score: 1, Informative

      MS has never shown the initiative to make things compliant

      Internet Explorer was the first browser with CSS support. It was the first browser with XSLT support. It was the first (mainstream) browser with XML support. It's the only browser with P3P support.

    10. Re:Why Bother? by 10101001+10101001 · · Score: 1

      You'd be more correct in saying "If you are making a *commercial* web page and you are not coding so that is renders correctly on IE you are a fool." It's hardly foolish to be obsessed with being absolutely sure that 85%, let alone 100%, of people view your personal web page. Personally, my web pages end up being so minimal that even bad rendering would at worst just make it look ugly. The whole point of the web is to display content. So long as content is out there and I'm not going out of my way to make pages render well in only brand X browser, I really don't care if any specific browser misrenders the page. When developing personal web space, I don't feel it my responsibility to include everyone. Of course, I guess my biggest reason for saying all this is because my web pages are so minimalistic that even lynx and dillo can display them well. So, it'd have to be a pretty fucked up browser to misrender my pages. As others have stated, it's the fucked up way in which IE handles pages that has slowed down any goals of mine in making any complex page for the concern it might not render properly in all sorts of browsers that a person might use which I cannot be goaded to check against just to not piss lots of people off.

      --
      Eurohacker European paranoia, gun rights, and h
    11. 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.

    12. 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.
    13. Re:Why Bother? by jbplou · · Score: 1

      50% of people don't know how to get a different browser than the one that came with their computer, a lot of home users can't even figure out Windows Update which is two or three clicks. You have to write your pages for your audience not try and change your audience if you are writing a site. Just because you like Konqueor doesn't mean your sites vistors will use it because you want them to.

    14. Re:Why Bother? by That's+Unpossible! · · Score: 1

      "Slowly but surely" is the most bullshit phrase in the English language.

      While that is true now, slowly but surely it is gaining respect!

      --
      Ironically, the word ironically is often used incorrectly.
    15. Re:Why Bother? by cpeterso · · Score: 1


      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.

      I code to standards. If IE does not display my web site correctly, then it is MICROSOFT, not me, who loses out.

    16. Re:Why Bother? by djrosen · · Score: 1

      Lets deal with it not being the best:

      Who cares that its the one individuals are using TODAY? Firefox is breaking through, more and more people are downloading and using it INSTEAD of IE reagrdless of what comes installed. Supported? By Who? Supported in that it comes with OS. Are you somehow insinuating that someone would not get support when they called DELL with a problem because they choose to use FF over IE?

      Lets address you being a moron and feeling the need to insult rather then just express your OPINION as I have shall we? Slowly but surely is exactly what is happening, dont like the phrase? Too Bad. How about Firefox downloads increase daily which more and more people are at least TRYING it but of course you never defend your statement, you just felt like calling someone a moron.

      Saying good riddance is completely feasable. Just becasue your portfolio is full of MS stock dosent mean its the only browser that users will like/use regardless of what is installed. I bought a new PC from Dell, formated it and installed Linux. Who said anything about RAPID adoption? Fact is, its happening at a rate fast enough to make MS notice and think about what they need to do to bury this browser as well, thing is, it isnt happeing this time. As for Linux OS adoption, I wont even touch it as you are obviously the clueless moron youd like to make me out to be.

    17. Re:Why Bother? by danielrose · · Score: 1

      77% of all statistics are nonsense! 48% of people know that!

      --
      i hate pansy republicans
    18. Re:Why Bother? by djrosen · · Score: 1

      I dont get this whole FORCED arguement. If developers coded to the standard rather than the browser as they SHOULD be doing, this would be a moot point. If you come to MyBank.com and IE doesnt work you will switch to one that does, the same way you use IE now when when Firefox doesnt work.

      Do you think that Joe Luser will take all his money out of MyBank just becasue he had to DL a different browser to do his online banking?

    19. Re:Why Bother? by djrosen · · Score: 1

      It should be the other way around. Web Coders should become more standards compliant, waiting for MS to do this is like watching water boil while the stove is off.

    20. Re:Why Bother? by AK+Marc · · Score: 1

      If you are making a web page and you are not coding so that is renders correctly on IE you are a fool.

      I'm so glad that I'm surrounded by fools. There is a mandatory web site for some of my classes. It lets people know that it doesn't work in IE. You want to pass your class? You have to download and install another browser. The fault is all Microsoft. The page is built to standards, then they found out later that IE will not properly open and save files (IE tries to open files directly, even when told not to). So, the solution is to let people know that Microsoft is not usable, but Safari, Firefox, and others are.

      Yes, it was foolish to design a web site to standards and expect IE to open it correctly. But if you find yourself in that situation, which is more foolish, redesigning a web site to accommodate a broken browser, or inform people that they may use it, but the results are not as intended?

    21. Re:Why Bother? by 2short · · Score: 1

      If webmasters don't code for IE, they'll get fired and replaced with more people interested in reaching their audience than making a political point; no matter how valid that point may be.

      Asking webmasters to write pages so that they don't look good for more than 80% of their users is pointless.

    22. Re:Why Bother? by Anonymous Coward · · Score: 0

      This is now the 3rd stupidest thing I've ever read on dotslash.. err slashdot.

    23. Re:Why Bother? by Low2000 · · Score: 1

      I know that... but the parent asked how making IE more standards complient would help the Opera developers. It's difficult to get web coders to conform to standards if the most widely used browser out there is not standards complient. So, by trying to influence the most widely used browser to be more standards complient, you influence the masses of web coders. I'm not saying it's the best answer, it was a responce the the parent.

    24. Re:Why Bother? by Anonymous Coward · · Score: 0

      Renders correctly in IE? What version of IE on what version of Windows/Mac? They all have different quirks. Hard to code for the consistent IE standard when IE has no real standards and isn't very consistent either.

      In all honesty it's not about coding so that it renders "correctly". It's a matter of what is acceptable for quirks between browsers. It's been that way for years, and it's not going to change in the near future. Anyone who codes a page that is unusable in ANY browser is a fool. They're also lazy and probably shouldn't be coding HTML int he first place.

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

    26. Re:Why Bother? by Anonymous Coward · · Score: 0

      It did CSS first, but it did it *wrong*...

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

    28. Re:Why Bother? by jbplou · · Score: 1

      If your making a web site for a company its them who loses out. If your making a web site for a charity they lose out. If your making a web site for a college they lose out. No browser is 100% standards compliant with everything W3 puts out, not even Firefox. Best practive for a commercial/general public site is code for IE and Netscape/Mozilla/Firefox varient. Ideally you don't put anything out there that doesn't render correctly on IE or Firefox and you got a good site for the general public. If your working on an intranet site and you know what your users are using go ahead and code for a browser if not, don't be stupid and cut off your head to spite your face.

      Also I remember back in the late 90's when IE was more standards compliant than Netscape.

    29. Re:Why Bother? by Mattintosh · · Score: 1

      True, but if you write your code as "strict" code, IE will perk up and look almost right. Which is good enough (it's about time "good enough" got used against Microsoft). And if there's any sort of security setup on your site, or if you just want to blow smoke, you can put a note on the page that says "OMG YOU'LL GET OWN3D BY VIRII IF YOU DON'T USE FIREFOX" (or something to that effect) and get the boss to go along with it under the ever-present, ever-proud flag of fighting evil hacker terrorists trying to steal peoples' important data and rape their daughters.

      Wow... that was a long and poorly formed sentence. I'd like to see IE parse that.

    30. Re:Why Bother? by eugene+ts+wong · · Score: 1

      Well, you could always put this at the top/bottom of your pages:
      "This is best enjoyed with the Opera web browser."

      Don't force them. Educate them.

    31. Re:Why Bother? by Anonymous Coward · · Score: 0

      Internet Explorer wasn't just the first browser with support for CSS (Internet Explorer 3.0 on Windows), but it was also the first browser that supported virtually all of the CSS 1 specification (Internet Explorer 5.0 on the Mac).

    32. 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.
    33. Re:Why Bother? by tepples · · Score: 1

      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.

      There's a difference. At the moment, the latest version of Mozilla Firefox adheres to the current specifications of the World Wide Web better than the latest version of Microsoft Internet Explorer does. Microsoft has had several years to bring IE up to conformance with CSS 1, let alone CSS 2, but it hasn't.

    34. Re:Why Bother? by Anonymous Coward · · Score: 0

      85% where? March w3schools says 67%

  • 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.
  • 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. Re:Standards, schmandards... by rob_squared · · Score: 1
      And if I kill more people than the government, then I get to decide if murder is legal?


      I don't think so.

      --
      I don't get it.
    5. Re:Standards, schmandards... by tepples · · Score: 1

      And if I kill more people than the government, then I get to decide if murder is legal?

      Yes you do. It's called a revolution. One happened on the east side of North America in the 1770s.

    6. Re:Standards, schmandards... by reclusivemonkey · · Score: 1

      Yeah? What happens when your monopolistic empire crashes and burns like every other one throughout history? Standard compliance is the future. Anyone with half a brain cell already gets that.

  • Re:Like say the same joke everytime? by ScentCone · · Score: 1

    You win. At least my loserness is attached to my user account, you AC.

    --
    Don't disappoint your bird dog. Go to the range.
  • 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.

    1. Re:Great Strategy by madgeorge · · Score: 1

      You just did. :)

    2. Re:Great Strategy by The+Cydonian · · Score: 1

      I think Hakon raised this challenge less as Opera's CTO, and more as the creator of the original CSS standards.

    3. Re:Great Strategy by Anonymous Coward · · Score: 0

      Wow, sounds exactly what Mozilla keeps doing!

    4. Re:Great Strategy by setmajer · · Score: 1

      The post is misleading (there's a first ;-). Opera isn't developing the test, the Web Standards Project is. I know -- I'm on the dev list for it.

      There *are* a couple of Opera folks working on the test, but the current dev version of the test also exposes some bugs in their browsers (and in Firefox).

      I can't speak for either the WaSP as a whole or all the folks working on the Acid2 Test, but personally I'd welcome input from MS folks as well. The more weaknesses the test exposes in all browsers, the better AFAIC.

      --

  • 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!
    1. Re:I want IE7 to... by rcamans · · Score: 1

      Don't worry. Based on past history, MS is going to grant your wish in a big way.
      So, yes, that is a valid "choice", although you do not actually have any say in it.
      The word choice is usually restricted to cases where you have more than one possibility.

      --
      wake up and hold your nose
    2. Re:I want IE7 to... by Anonymous Coward · · Score: 0

      Not only a valid choice, but the one that was choosen!

      By the way, you are late for taping your new AOL commercial.

    3. Re:I want IE7 to... by Anonymous Coward · · Score: 0

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

      It wasnt? I just clicked Yes To Continue...figured it would be the equivalent

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

    2. Re:Why take up the gauntlet? by Anonymous Coward · · Score: 0

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

      "Go download Firefox."

      Maybe in heaven that is what you could say. In reality, you'd say something like this:

      "Oh shit, I'd better fix that before I'm fired!"

      Web developers just don't have the luxury of telling 90% of their visitors to download another browser.

    3. Re:Why take up the gauntlet? by rpdillon · · Score: 1

      Sorry, I didn't make myself clear...that URL was supposed to imply a location where the "standards test" would be located. In this case, people would visit it because they saw a link in some news article entitled "Is Your Browser Hot or Not?".

      The webpage would be designed for the sole reason of telling people to download a different browser. It would be, by definition, standards compliant, and would have no purpose than to break browsers that did NOT follow those standards.

      Should've made that clearer, I suppose.

    4. Re:Why take up the gauntlet? by Fjandr · · Score: 1

      This goes back to "What do they have to gain?"

      Only in the event that there is publicity surrounding their failure to address the issue would it conceivably harm them. There is an entrenched user base for their product, particularly around the common demographic of those people who are unaware of competition and probably wouldn't be bothered to change if they were aware.

      Among those who already have an understanding of the issues, there is usually ample capability to change and deal with the ramifications of those changes.

      Microsoft has been rewarded for paying lip service to compliance while failing to implement the same in their products. I still see no real reason why they would choose to actually address the issue at this time. It's not hurting their bottom line at the moment, and there's no accurate forecast to predict that it will in the near future.

      I wasn't saying that a test page is a bad idea, just that there's no real reason for Microsoft to take the challenge seriously (in practice, even if they appear to take it seriously from a PR perspective). I understand and agree with many of your points, but much of it requires that there is popular media coverage of the issue and enough people (who otherwise would not have bothered switching) end up switching away from their browser as a result. I'd love to see and end of IE dominance in the market. I think it's a horrible, slow, bloated monstrosity. From Microsoft's standpoint though, it's successful in spite of itself.

    5. Re:Why take up the gauntlet? by IntlHarvester · · Score: 1

      What do they have to gain (at this point) from actually producing a standards-compliant browser?

      Improved Dev Tool support, plus developer eyeballs. You see the hated here from people who believe that IE is old/broken/buggy. In the CSS world it's the reincarnation of Netscape 4 ..

      Plus, MS has spent the last few years hyping XML, so the lack of XHTML support stands out like a sore thumb.

      --
      Business. Numbers. Money. People. Computer World.
  • 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.

  • your right by Uptown+Joe · · Score: 0

    MS tells us what we want not the other way around...

  • 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 Anonymous Coward · · Score: 0

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

      That link you posted displayed just fine in IE -- it sent me straight to Windows Update, and allowed me to download the latest updates to Internet Explorer, without any display issues whatsoever.

      Looks like Microsoft's already ahead of the game!

    2. 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.
    3. Re:My proposal for the test page. by Anonymous Coward · · Score: 0

      Maybe, fucknuts, it was a joke. Ever think of that? Or did you miss the Funny moderation?

      Why does no one on Slashdot have a sense of humor?

    4. Re:My proposal for the test page. by Anonymous Coward · · Score: 0

      I think you missed the screenshot. Try going back and taking another (or, rather, a first) look.

    5. Re:My proposal for the test page. by Anonymous Coward · · Score: 0

      I saw it - it's a screenshot of IE showing the page. Wow. How funny. No kidding, you mean the webpage actually works in IE? Amazing.

      See, unlike fucknuts up there, I actually got the joke: as long as people can download Firefox, who cares if it supports web standards?

      Fucknuts didn't get it, and instead has to post a screenshot of it working normally.

      I can only assume those funny mods are pity-mods for someone too dumb to get an obvious joke, which is pretty funny.

  • It wouldn't fit on one web page by ozziegt · · Score: 1

    At least not reasonably. There are too many different cases and uses to test. A large majority of web designers (even the best ones) only use a small portion of what CSS can really do. Making an acid test web page can be done, but it would be tens if not hundreds of pages to go through.

  • 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?

  • 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
    1. Re:Opera is already dead. by Anonymous Coward · · Score: 0

      ding ding ding ding! they just want pub. CTO needs to get a life and focus on his own shitty browser. sorry folks, no way i'll pay for a web browser!

    2. 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
    3. Re:Opera is already dead. by Saeed+al-Sahaf · · Score: 1
      Really. Which ones? More than any? Drugs. Are. Cool.

      I have no problems with Opera tooting their horn, but people need to understand that Opera is not FOSS / Open Source / Next To God. They are a commercial product just like Microsoft, looking to tap into a market. There is nothing wrong with that, but they are not the Holy Open Source Application. Just a nice company. With a quirky funny web app.

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    4. Re:Opera is already dead. by Saeed+al-Sahaf · · Score: 0, Flamebait
      As I understand it, Opera runs on more devices than any other browser.

      So... you don't actually use Opera. I'm not suprised, I've been looking for actual Opera users for years. Not sure who they are, but I sure don't know any.

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    5. Re:Opera is already dead. by bhtooefr · · Score: 2, Interesting

      First off, Opera's still innovating. Who has voice? Not Firefox, that's for sure... Who has small screen rendering? Not MiniMo (yet, anyway)...

      And, I've heard Opera's biggest moneymaker is NOT the desktop, where one can pay $0 and get text ads instead. It's mobile, where they're the only good game in town on some OSes (and they're working on Windows Smartphone - Pocket PC and Palm will be the only major OSes lacking Opera).

    6. Re:Opera is already dead. by the+arbiter · · Score: 1

      You do now. I've been using it as my main browser for 2+ years now. It's fantastic, except for those few sites that have chosen to use IE-only code.

      A good product. Renders quickly.

      What got some money out of me for them, though, was the mail client. It's SO easy to use and just does mail.

      --
      Boycott everything - they're all trying to fuck you one way or another
    7. Re:Opera is already dead. by jthayden · · Score: 1
      http://www.opera.com/company/investors/finance/200 4/4Q04_presentation.pdf
      http://www.opera.com/company/investors/finance/


      There balance sheet is looking just fine. Yeah, Firefox will take a bite out of them, but the majority of their money is coming from the wireless market not the desktop.

      In the first link, you can find a long list of the phones and PDAs they support and they are the default browser on many of them. I don't know about the more than any though.


      No, Opera is not open source, but not everything needs to be. If everything was open source, who would employ all those pasty skinned, unshaven developers? Just because something is open source doesn't mean it's great and just because something is a comercial product doesn't mean it sucks.

    8. Re:Opera is already dead. by oddfox · · Score: 1

      Someone wake up on the wrong side of the bed today or what? For your first response to badmammajamma, I don't see what point you're trying to make. It's not open source, it's not free, so what? You're nitpicking, and completely ignoring the fact that Opera has been around for quite a while, with the first Windows version being released in '96. A quick Google search reveals this Q42004 presentation that apparently shows them not doing so hot, and I think that maybe the advancement of Mozilla/Firefox has bitten into at least a small portion of their market.

      And maybe you should try using Opera sometime, it's a good, lightweight and fast web browser, and the Google ads in the free version take a grand total of 30 PIXELS in my titlebar for Opera. Truth be told, I have just as much screen space for the actual website and not the application in Opera than in Firefox! Internet Explorer still gives me the most though w/o the Google toolbar yet installed and showing.

      I've been a fan of Opera since 4.x for it's speed and small size, I have never paid for it, I hardly ever had it installed until I got into web development and decided to make sure my pages look fine in it as well. Hell, I like the beta for Opera 8 enough to consider purchasing it, but when those text ads only take up that tiny amount of space... I dunno, I must have selective sight. comparison of toolbars in FF/Op -- Turns out my Opera and my FF are on par for space taken, and these are the DEFAULT layouts.

      Probably a troll anyways who has never used the program him/herself and would rather rag on it all the time as if he/she knew anything about it.

      --
      "We invented personal computing." - Bill Gates
    9. Re:Opera is already dead. by scoobrs · · Score: 1

      Who cares if they aren't open source? I just need something fast with real sessions and MDI that doesn't hog my memory or invite spyware in. Web standards only matter when things actually don't work. Is anyone reading this tripe an engineer who actually cares about best tool for the job anymore? Some people use browsers and operating systems to do paying work. So what's wrong with using Linux and Opera?

      --
      -Those who would give up essential liberty to purchase temporary safety deserve neither. -Ben Franklin
    10. Re:Opera is already dead. by Anonymous Coward · · Score: 0

      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.

      I move that all posters that use "or die" while pretending they know what business model a certain company or project should use be immediately modded down "-5 douche bag" and automatically give up their slashdot membership. It implies armchair quarterbacking, which is annoying and pointless. Who's with me?

    11. Re:Opera is already dead. by Anonymous Coward · · Score: 0

      Second that one.

    12. Re:Opera is already dead. by LPetrazickis · · Score: 1

      Hi. I am an actual Opera user on both Windows and Linux.:)

      I check up on Firefox regularly, but it's not even trying to compete with Opera. It's very easy to juggle Opera's interface elements around visually, and I don't need to dig through a huge repository of extensions to get 50% of Opera's perks.

      --
      Is this a sigs-optional kind of place? 'Cause I am totally down with that if you know what I mean.
    13. Re:Opera is already dead. by Anonymous Coward · · Score: 0

      Well, if their main moneymaker is mobile platform, it is very sad, that their current version is 6.something. Of course, Netfront kicks Operas' butt anyway.

    14. Re:Opera is already dead. by untouchable · · Score: 1

      HAHAHA. Oh lord, you're serious. NetFront stinks to high heaven. When you can have more than one browser open in NetFrontv3.2 (which I believe is the latest version) and actually render a page in a decent amount of time, then I'd consider Netfront vs. Opera.

      --
      As Seen On TV's? Come back!!!
    15. Re:Opera is already dead. by Saeed+al-Sahaf · · Score: 0, Troll

      Ouch! Three fucking paragraphs! Life? Do you have one?

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    16. Re:Opera is already dead. by oddfox · · Score: 1

      Right, troll it is. Just remember how many posts you've made on this topic as opposed to my single post, on my day off even.

      --
      "We invented personal computing." - Bill Gates
    17. Re:Opera is already dead. by jp10558 · · Score: 1

      Oh, I don't know. I could change two words up there and make a similar "common sense" statement that we all know is wrong:

      Basing your business model on selling water is not going to make it.

      Opera does all right. It's a niche market, but so what? Last I heard Aston Marton does ok also.

      And Opera 8 has many people salivating, even non fanboi's.

      Other people have pointed this out, but haven't really taken this too far. Opera is pretty big on Mobiles. Mobiles are overtaking desktops for internet accessing devices. Having a huge presence on Mobiles can have a network effect. How many people want Word at home because that's what they use at work? Well, there is a chance that some people might want what they got used to on their cell on their desktop. Especially with younger people.

      --
      Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
    18. Re:Opera is already dead. by limon.verde · · Score: 1

      Actually, they may not be willing to make a browser for mobile phone Microsoft platforms, as payback for a bad play MSN had on Opera. Also, Opera for the desktop is one of the best applications I have ever seen. No other browser allows a PII with 384 megabytes of RAM have 200 open pages, without slowing down at all. It is an amazingly flexible browser, that can be molded to your prefferences without a hitch, and without extensions (that may or may not be updated with your browser). It's keyboard and mose shortcuts are impressive. Furthermore, you have the ability to browse safely all the time. Entered a page that requires java/javascript/a pluggin/refferer logging? press F12 and enable it for the ocasion... if you trust the site. I really don't think they consider desktop browsers a side job.

    19. Re:Opera is already dead. by Anonymous Coward · · Score: 0

      Opera already has a browser for Windows Mobile. Duh.

    20. Re:Opera is already dead. by WIAKywbfatw · · Score: 1

      Sorry, but you are trolling now and you know you are. For the record, I'm yet another Opera user. Several people I know (all IT professionals, most of them with 15+ years experience) are too.

      --

      "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
    21. Re:Opera is already dead. by badmammajamma · · Score: 1

      Actually I do use Opera.

      --
      Any man who afflicts the human race with ideas must be prepared to see them misunderstood. -- H. L. Mencken
    22. Re:Opera is already dead. by badmammajamma · · Score: 1

      Sucks to lose an arguement, eh?

      That's ok...mommy will make it all better *smooch*

      --
      Any man who afflicts the human race with ideas must be prepared to see them misunderstood. -- H. L. Mencken
    23. Re:Opera is already dead. by Anonymous Coward · · Score: 0

      I'm using Opera for the first time today (because, very unusally, the FreeBSD guys broke the mozilla port during the XFree86 to xorg transition (nsFreeType.cpp guys btw)).

      I'm pretty impressed with it.

      All the usual - trivial install, tabs, pop-up blocking, nippy, picked up all plugins OK, easy to set and sensible prefs, nice zoom function and restores session after crashing (prob due to aforementioned xorg issues) - very nice! It's even got free babes in the ad bar + the mime.types list makes a lot more sense than in moz.

      I'll certainly be keeping it installed as a 2nd browser.

    24. Re:Opera is already dead. by limon.verde · · Score: 1

      You're right!! thank you, and I 'm sorry... That'll teach me against posting pseudo-facts from memory without checking first!

  • Acid test by y0saph · · Score: 1, Funny

    *Testing if code is Acid* *Code is BASIC*

    --
    I can now stop time, but the effect is only temporary
  • It would take... by Edward+Teach · · Score: 1

    an entire web site to fully test w3c standards, css-1, css-2, javascript, etc. One page isn't going to do it.

    --

    Setting his threshold to 5, Sparky eliminated most of the trolls on /.

    1. Re:It would take... by ciroknight · · Score: 1

      Good thing W3C.org is full of tests for each of the standards you mention.

      PS, it all could be done in one page, since no test excludes another, AFAIK. It'd just be one bitch of a webpage to code, to load, and to read the results from.

      --
      "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    2. Re:It would take... by Sparr0 · · Score: 1

      One page would be fine. It would just be one very 'busy' page, with hundreds of elements visible on the screen. You would handle it like an image rendering test, comparing a screenshot of the 'reference' implementation to what the browser spits out.

  • I hope not! by Anonymous Coward · · Score: 1, Interesting

    I don't want my browser doing what many web "designers" want it to do. I want my browser to do what I want it to do. The challenge is a bit misleading, or its restatement is. The browser should be capable of doing things in a standards compliant manner. Too many web designers (or designer wannabes) want to do stupid, irritating things. Nobody has to let them.

    1. Re:I hope not! by Anonymous Coward · · Score: 0

      You've been able to do this for years with Opera (since at least Opera 4). For any webpage, you can turn off document CSS, making the browser ignore (more or less) all formatting instructions within the document, and use your own setup.

      I've been doing this for ages, I see webpages with the colors and fonts that I like, not those that the web author likes. If I want to, I can always switch to the author's formatting with the push of a key. Notice how I never complained about it.slashdot's crazy color scheme? That's because I never saw it.

    2. Re:I hope not! by Anonymous Coward · · Score: 0

      BTW, I believe Firefox/Mozilla has finally caught up with this... years later.

  • 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

    1. Re:Yeah, so... by theapodan · · Score: 1

      Good point, and the fact that IE7 will not be available for pre-SP2 Windows XP, a good deal of those older IE 6 users will still be around.

      Of course, Windows Update could start listing firefox as the browser upgrade for Windows 98-2000.

    2. Re:Yeah, so... by Anonymous Coward · · Score: 0

      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.

      A file upload script? There isn't a standard way for Javascript to access the host filesystem, so Safari's problem isn't lack of compliance with standards.

      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.

      30-40% of the market uses Netscape 4.7 and Internet Explorer 5? What market are you talking about? Your numbers are way off base for the web.

    3. Re:Yeah, so... by drew · · Score: 1

      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.

      your current browser apparently has a bug which causes it to insert spurious 0's into textareas while typing. i believe you meant to type "3-4% of the market".

      you might want to check if there's a patch available for that, it could really mess you up if you do any kind of bill payment online.

      --
      If I don't put anything here, will anyone recognize me anymore?
    4. Re:Yeah, so... by slapout · · Score: 1

      It's not like Opera hasn't been provoked.

      --
      Coder's Stone: The programming language quick ref for iPad
    5. Re:Yeah, so... by Anonymous Coward · · Score: 0

      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

      I'm not going to, neither would do most of web designers who conform to web standards. If you use Netscape 4 or IE below 5 you're going to see a website without the style sheet to see the information. If you use IE5 or 5.5 you're going to get the stylesheet, but don't complain about alignment of elements. Period.

    6. Re:Yeah, so... by knight37 · · Score: 1

      It's not windmills. They are doing this just to get slashdotted. They need constant exposure and generating "controversy" helps generate sales.

      --
      Knight37 - Once a Gamer, Always a Gamer
  • 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
    1. Re:In other news... by Anonymous Coward · · Score: 0

      Then why do they keep talking smack about linux?

      http://www.microsoft.com/windowsserversystem/facts /default.mspx

    2. Re:In other news... by Anonymous Coward · · Score: 0

      Here's where your analogy between Open Source/MS and US/China fails: Open Source geeks already make a pretty secure OS.

  • Re:Like say the same joke everytime? by ScentCone · · Score: 0, Redundant

    OK then, how about Trusting The Karma. Just trying to avoid the spam, dude. I don't care what a user's name is, and there are time when anonymity makes perfect sense (say, when your job may be at stake)... but ad hominem attacks aren't one of those times. Leave a trail when you're hassling somebody - it's only sporting.

    --
    Don't disappoint your bird dog. Go to the range.
  • Slashdot != xhtml by Arbin · · Score: 2, Interesting

    Slashdot produces some of the worst html code available, and it doesn't produce the same exact code EVERY time. Some days it offers spans, some days tables missing end tags, it's just random garbarge. How do you expect ANY browser to render code the same, EVERYTIME? God. I fed a troll... *shaking head*

    1. Re:Slashdot != xhtml by Anonymous Coward · · Score: 0

      It would be interesting to see how this site performs if it was written in ASP.net and see how that html looked

    2. Re:Slashdot != xhtml by Anonymous Coward · · Score: 0

      Hm, no not really. the HTML you get out of ASP.NET is what you make it, notwithstanding a few automatically generated things.

      I was (at a former job) a web developer, and our sites were great in any environment we coded against, because our HTML coders were good and knew their job.

      Pretty crappy troll.

  • wasting time? by bogaboga · · Score: 1
    I will answer myself. This guy is wastimg time. He thinks M$ will listen? I wish him the best. It's like talking to a statue, hoping to get an answer. I wish him luck. I suggest the following: -

    Let the other browser creators build a site, publisize it and ashame M$. This might work but no guarantees.

    1. Re:wasting time? by Luchio · · Score: 1

      Let the other browser creators build a site, publisize it and ashame M$. This might work but no guarantees.

      The Acid2 test will not be built by OperaSoft but by the developpers of The Web Standards Project.

  • Double Edged Sword (XMLHttpRequest?) by Bronz · · Score: 1


    I've been an Opera supporter for years, but at some point it must become evident that Hakon Wium Lie (and other Opera employees) are simply venting frustration.

    While I think the acid test is great, Opera has been uncharacteristically silent on getting XMLHttpRequest up to the Firefox/Safari/IE level. I know Opera will tell you "it is coming in version 8", but I thought the position of the one commerical browser of the bunch was to lead, not follow.

    P.S. Why do all the Fire/zilla mouse gesture packages use nearly identical mouse gestures from Opera with the exception of [right button]+down is new window instead of new tab? As an Opera *and* Firefox user, this is frustrating.

    1. Re:Double Edged Sword (XMLHttpRequest?) by Anonymous Coward · · Score: 0

      It is in version 8. Grab the beta, it's worth it.

    2. Re:Double Edged Sword (XMLHttpRequest?) by Luchio · · Score: 1

      While I think the acid test is great, Opera has been uncharacteristically silent on getting XMLHttpRequest up to the Firefox/Safari/IE level. I know Opera will tell you "it is coming in version 8", but I thought the position of the one commerical browser of the bunch was to lead, not follow.

      The XMLHttpRequest works really good in the latest Opera 8 betas. It IS implemented. As for CSS 2.0, it has been in Opera a long time ago.

      Why do all the Fire/zilla mouse gesture packages use nearly identical mouse gestures from Opera

      Mouse gestures can easily be edited in Opera preferences to match what you really want. It's interesting to note that the idea of mouse gestures came from Opera before it was copied by FireFox/Mozilla (Though I don't blame them, it's a great feature!).

    3. Re:Double Edged Sword (XMLHttpRequest?) by endx7 · · Score: 1

      Tabs came from opera too.

      I remember them way back when in opera 6. I used mozilla, but it crashed a lot and was slow, and someone suggested opera. I'm glad they did, cuz tabs are neat-o.

      I still use opera most of the time, mostly because I don't like firefox's tabs unless I install a bunch of extensions. Even then, it still doesn't feel right.

    4. Re:Double Edged Sword (XMLHttpRequest?) by vonsneerderhooten · · Score: 1

      Likewise, I actually shelled out the 30 bucks for the legally ad- free opera 6. They also promised me a "power pack" to be received in the mail. T- shirt, coffee mug, etc. Never got it. I did get my free upgrade to 7 though.

      I don't use opera anymore. last version i used was 7.51. Using firefox and though it's better i love the tabs and gestures in opera.

    5. Re:Double Edged Sword (XMLHttpRequest?) by The+Cydonian · · Score: 1

      Hasn't XMLHttpRequest been supported since v7.54? I mean, wasn't that the point of that release?

    6. Re:Double Edged Sword (XMLHttpRequest?) by hkmwbz · · Score: 1
      What, exactly are you trying to say?

      Just because Opera implements something after Firefox doesn't mean that it always follows others. Most of the features Firefox brags about were pioneered by Opera! Google search field, popup blocker, etc.

      I really don't understand what XMLHttpRequest has to do with Opera "venting frustration" at all. What are they venting frustration at?

      Please explain.

      --
      Clever signature text goes here.
  • That's it... by Infinityis · · Score: 1

    I know what they should do...get all the browser companies together to create a BlueBrowser Special Interest Group (SIG), and define standards for interoperability. Then, to top it all off, create a special logo that can only be used by browsers that meet the rigorous testing and qualification requirements that ensure BlueBrowser software will render webpages properly.

    Nah, who am I kidding...That sort of thing would never take off.

  • 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.
  • Kettle: you're black. by Anonymous Coward · · Score: 0

    Opera, complaining about standards conformance, thats comical at best. Anyone ever tried to develop for that peice of junk. Its dom implementation tries to pass itself off as ie compatible so much without ACTUALLY BEING IE COMPATIBLE that it makes it almost impossible to write for without putting in special checks to make sure its not opera. Then they bugfix something and bitch about people doing it. And dont even think about trying to use liveconnect, man that browser dies a thousand deaths for every liveconnect page that works properly.

    Go back to rendering plain html+css. I'll keep ie for my web applications.

    1. Re: Kettle: you're black. by hkmwbz · · Score: 1
      "ts dom implementation tries to pass itself off as ie compatible so much without ACTUALLY BEING IE COMPATIBLE that it makes it almost impossible to write for without putting in special checks to make sure its not opera."
      Competent web developers would check for standards compliant browsers first, so that Opera gets standards compliant code.
      --
      Clever signature text goes here.
  • Lost cause? by Nik13 · · Score: 1

    No matter what people ask for or do, I don't think it will have it all. They might at some point in time have been leading, but right now they're playing catch-up big time.

    Full, proper CSS support (including complex selectors) is just a start. We also very much need it to support standards (like support the <abbr> tag, not just <acronym>), including standard voice+xml technology as well (but I can't see that happen). If they don't use the same things as the rest of the world will use for that, then it just makes it harder for us to use the new technology, as a good portion of browsers won't support it (same thing about XForms or whatever). Their proprietary stuff prevents us from using these useful technologies. I think we don't need another ActiveX-like thing. It's their chance to prove us they're serious about their claims of interoperability (and security), but something tells me we'll be really deceived again. (And I didn't even ask for niceties like firefox style extensions, tabbed browsing or anything - just a good standards-compliant browser)

    --
    ///<sig />
  • 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...
  • 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

    1. Re:Why would Microsoft care? by Coryoth · · Score: 1

      Opera is an increasingly marginalized player in the browser market.

      I think you might be surprised. Opera has a decent popular following in the desktop market. Sure, it's not growing, but it's not shrinking either. More importantly though, Opera has a very strong position in the mobile/embedded market where their "small and efficient" approach pays dividends.

      Don't forget, either, that Opera has been a continuing source of innovation in the browser market: tabbed browsing and mouse gestures showed up first in Opera. They've recently also added native SVG support out of the box. No, these aren't startling innovations, but they do help to keep the browser market active and moving forward.

      And just for reference, no I'm not an Opera fanboi. I use Galeon myself, but I used to use Opera when I was on Windows (back before Firefox existed), and have at least kept track of what they're doing.

      Jedidiah.

    2. Re:Why would Microsoft care? by jp10558 · · Score: 1

      I don't know about that. More and more (in the past 6 months) web sites I've used have re-designed their interfaces to work in Opera.

      Streamload.com, Buffalostate.edu and maps.google.com being noticable examples (and not necessarily ones I would expect).

      OTOH, Ameritrade.com just designed their new site to be IE only, and GMail is still a pita so what do I know (I'm trying to figure out how to actually close my account there, I may have to call them).

      --
      Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
    3. Re:Why would Microsoft care? by hkmwbz · · Score: 1
      "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)."
      Sorry to break it to you, but Opera has been around for ten years, and has more users and more money than ever before. It's really gaining a strong foothold in the mobile market, where nothing is even close to touching it. Minimo might give it some competition, but Opera has years of experience with mobile browsers, so it's not going to be easy.
      --
      Clever signature text goes here.
  • We don't need them to drop acid by Sebby · · Score: 2, Funny

    with the way MS products behave, it's obvious they've had acid before!

    We need them to learn to read specs!

    --

    AC comments get piped to /dev/null
  • 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.

  • Self-serving propaganda by Anonymous Coward · · Score: 0

    If MS made IE7 "a browser worth having that will do the Web good" his company (Opera) would be out of business! Not that his distant-third browser matters to anyone anyway!

  • Word of the day... by HerculesMO · · Score: 1

    'quixotic'

    Damn I love Firefox's dictionary search extension :)

    --
    The price is always right if someone else is paying.
    1. Re:Word of the day... by elcid73 · · Score: 1

      I like Opera's extension for that too! Oh... yeah, it's built in to the browser.

    2. Re:Word of the day... by AK+Marc · · Score: 1

      Ain't that the truth. Every time I talk about a feature I like in Opera, the resident Firefox guy talks about all the extensions you can add in to make it almost as good. Yeah, except compare the speed of a fresh install of each. Almost equal. Now, add in all the extensions for the features in Opera I like and use on a regular basis. You find out that Firefox isn't as slim and quick as people say.

    3. Re:Word of the day... by KillerDeathRobot · · Score: 1

      Yeah, but the really cool feature Firefox has over Opera is that it doesn't have that ad bar across the top.

      --
      Thinkin' Lincoln - a web comic of presidential proportions
  • 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 cayenne8 · · Score: 1
      "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."

      Frankly, if IE handled the 'Box Model' correctly, for css....it would be a HUGE improvement...I hate having to do kludges for IE...

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    2. 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.

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

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

    5. Re:Sometimes, IE renders bad HTML well by Frank+Dreben · · Score: 1

      IE renders bad HTML because that "bad HTML" was probably written using IE as the reference browser.

      "IE renders bad HTML written for IE better than the other browsers" is a more accurate statement.

    6. Re:Sometimes, IE renders bad HTML well by Curtman · · Score: 1

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

      How is it any different? With HTML, the user is the web developer, just as the programmer is the user of C or C++. The person viewing the page is analogous to the user who uses the program after it has been compiled.

    7. Re:Sometimes, IE renders bad HTML well by Anonymous Coward · · Score: 0

      No, because a web page is "compiled" in the user's browser, not on the developer's machine.

      The key difference is that if a programmer's code doesn't compile, he (as a programmer) can fix it. If your browser doesn't render a webpage, there's nothing the enduser can do but switch browsers. Therefore backwards compatibility old "broken" practices will ALWAYS be a very important competitive point for browsers.

    8. Re:Sometimes, IE renders bad HTML well by Anonymous Coward · · Score: 0

      > Browsers shouldn't render broken HTML

      The problem is that what you consider "broken HTML" was considered "just fine HTML" at one time. If your browser refuses to render it, like it or not, it's the thing that people will consider to be broken.

    9. Re:Sometimes, IE renders bad HTML well by Curtman · · Score: 1

      I disagree, because if the users are unable to view a page because it is broken, it will be fixed.

    10. Re:Sometimes, IE renders bad HTML well by earthbound+kid · · Score: 1

      Yeah, that problem's been fixed. If you tell Firefox that a page is an XHTML 1.1 xml/application in your HTTP header, it will suspend on error, which is handy for debugging the page. Still, nothing beats the HTML validator at w3c.org. That's convenient. Anyhow, all modern browsers look at the first line of the webpage to check for a "doctype" statement. Pages without a doctype get quirks mode (AKA Internet Explorer 4.0 emulation) and pages with a proper doctype are decoded in the proper way. Using these doctypes means that when CSS 89.2 comes out, browsers of the distant future will still be able to see that your page was coded in CSS 2.0 and switch to the appropriate rendering engine. Which means pages can be "future proofed" and you don't have to fear new browsers having a different way of rendering pages.

    11. Re:Sometimes, IE renders bad HTML well by shaitand · · Score: 1

      This assumes that the developer is using the same browser as the viewer.

    12. Re:Sometimes, IE renders bad HTML well by Curtman · · Score: 1

      No, just that the developer is aware of users who are unable to view his work. Or failing that, his boss being aware of him/her not caring.

    13. Re:Sometimes, IE renders bad HTML well by shaitand · · Score: 1

      "Or failing that, his boss being aware of him/her not caring"

      I'll give you that with one minor correction. His boss being made aware of him not caring in a way that he can not ignore. You have to remember, usually the boss really does not care either.

    14. Re:Sometimes, IE renders bad HTML well by ChatHuant · · Score: 1

      How is it any different? With HTML, the user is the web developer, just as the programmer is the user of C or C++. The person viewing the page is analogous to the user who uses the program after it has been compiled

      It may surprise you, but there are browser users out there that aren't web developers ;) .

      You're right, the person viewing the page is analogous to the user of the program. But the user of the program does not compile it, he uses it! That's why the compiler should be as strict as possible with errors, but the program itself should fail gracefully. And that's why the browser, which is instrumental in the usage of the web page (as opposed to its development) should be as resilient and forgiving as possible.

    15. Re:Sometimes, IE renders bad HTML well by Curtman · · Score: 1

      Yeah, if you approach someone with a comment like "Hey, I love your web page but $PROBLEM prevents me from going there anymore", you'll probably get a favourable response. If your first contact with them is a full out rant about Microsoft being out to destroy the internet, it probably won't go so well. Save that for later.

    16. Re:Sometimes, IE renders bad HTML well by oisteink · · Score: 1

      I'm not shure that trying to render broken HTML would be in the users interest. *You* might like gracefull fails, but to a user it just looks like an ugly page. Look it up in an HCI book - if you got any :P

    17. Re:Sometimes, IE renders bad HTML well by ChatHuant · · Score: 1

      I'm not shure that trying to render broken HTML would be in the users interest

      Come on. Most users will prefer a page which gives them the information they want, even if it's not precisely aligned, or uses a default font, to a page that only displays some cryptic error message.

      *You* might like gracefull fails, but to a user it just looks like an ugly page.

      Graceful degradation and graceful failure are basic principles of good software design. It doesn't specifically apply to web pages or browsers; any product that needs to be used in a production environment, or which is expected to have a large user mass should consider possible error conditions and try to deal with them nicely. You must also consider the capabilities of your target users; is there a point in displaying a big error message for a user that doesn't own the web page containing the error and can't do anything about it?

      Look it up in an HCI book - if you got any :P

      I'm talking about professional software, not applets, toy applications or web pages some amateur knocks out in his basement. If you don't have the time or inclination to handle graceful degradation, of course, it's your privilege. But don't be surprised when users will reject your product, because it won't do what they want.

    18. Re:Sometimes, IE renders bad HTML well by Curtman · · Score: 1

      The "viewers" are users of their browser software in my eyes. The HTML users are the ones writing the HTML. The person viewing the page is no more an HTML user than he is a C++ user, XUL user, and/or whatever user. Chances are he has no idea what language the browser or the web page are written in.

      Let the broken pages die. Good riddance to bad practices.

  • Broken? by gandell · · Score: 1
    That would simply not fly since most people are of the min "If it ain't broke, why fix it?"

    Tell that to Linux / Mac users who try to use the system. But I get your point...people who design to IE only aren't worried about standards. To them, IE is the standard.

    --
    Mercy was given to me by Christ...I must give the same to others.
  • Indeed. by gandell · · Score: 1

    I stopped using Opera as my tabbed browser when Firefox users designed the "reload every" tag. Why should I pay for a browser when I can get the same features through a free, open source one?

    --
    Mercy was given to me by Christ...I must give the same to others.
    1. Re:Indeed. by elcid73 · · Score: 1

      I can get the gimp for free too. That is totally better than Adobe

    2. Re:Indeed. by AK+Marc · · Score: 1

      I stopped using Opera as my tabbed browser when Firefox users designed the "reload every" tag.

      Can you easily save all your tabs without a plug-in? How about setting it to open back with all the tabs as when you closed it? Last I checked (and it has been a little while) those features were unavailable with Firefox. Tabs were obviously an afterthought added just to compete with Opera, and they had greatly reduced functionality. Just like Opera did mouse gestures first (boy, I wish they'd patented that), they did it first, they did it best. Why should I support second best that is always playing catch-up when I can use the original?

  • Validator by XanC · · Score: 2, Informative
    1. Re:Validator by northcat · · Score: 1

      Er, no, that's a link to test web pages, not web browsers. (don't worry, the other guy posted a correct link before you)

  • Just a thought... by Saeed+al-Sahaf · · Score: 2, Interesting

    Just a thought (many dead bodies spinning in graves), what if IE7 is the Tit, the Jones, the Cake, the next best thing to drugs, and secure? Will it be a sign of the apocalypse?

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    1. Re:Just a thought... by Anonymous Coward · · Score: 0

      Yes, that would be an undisputable sign of the apocalypse.

      So we have nothing to worry about then ;)

      Seriously, though. Microsoft products only get good enough to kill the competition, and no better. And you don't have to be better than the competition to kill the competition.

      IE7 will get some positive reviews for tabbed browsing, unfucked printing, and marginal CSS improvements. The problem is that this isn't why people are leaving IE in droves. They are leaving IE because they keep getting viruses and spyware. Microsoft's attempt to bundle antispyware features may mitigate some risk, but it won't stem the tide. Users still run as local admins. ActiveX is still a supported plugin mechanism [which, incidentally, doesn't usually work without the user being a local admin]. Connect the freaking dots, Microsoft.

    2. Re:Just a thought... by Saeed+al-Sahaf · · Score: 1
      Seriously, though. Microsoft products only get good enough to kill the competition, and no better. And you don't have to be better than the competition to kill the competition.

      So, you think it could be "better" than FF? As if anything could! It's not FOSS, how could it be "better"? It does not come with a GPL so how could it be "better"? It is written by non-open source C coders, so how could it ever be better?

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    3. Re:Just a thought... by WIAKywbfatw · · Score: 1

      You seem to be living in a rather strange world where anything that is F/OSS is automatically better than any commercial/CSS counterpart. How a piece of software is licensed has very little to do with how suitable it is to do its job.

      Is GIMP better than Adobe Photoshop? Is any F/OSS tool that's better than Macromedia Dreamweaver? Any that's better than QuarkXPress or Adobe InDesign? Any that's better than AutoCAD? Etc, etc.

      Stop assuming that the GPL or any other license automatically makes F/OSS superior than the alternatives if you want to be taken seriously, and stop pretending that it's how software is licensed rather than how it performs that constitutes "better" to all but a minority of individuals such as yourself.

      --

      "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
  • In an IE7 world.... by gardyloo · · Score: 2, Funny

    ...all links posted on slashdot go directly to Roland's webpage.

  • Opera? Compatibility? by leshert · · Score: 2, Interesting

    I'll be more impressed by something Opera says about compatibility when they fix their own issues--particularly their shoddy XMLHTTPRequest implementation.

  • Microsot is smart, although not ethical by PhatboySlim · · Score: 1
    As sad as it sounds, I highly doubt microsoft will enforce 100% compliance with web standards even though it would be very easy for them to do.

    Why do you ask? Simple. It's the same reason Microsoft has chosen to make everything different from the standard. As long as they control the operating system, they control the components of that operating system and people are more prone to use their products to maintain an industry standard.

    As soon as users can get exactly the same performance from IE as another browser then an even larger number of users will switch. The same holds true for any other component of that operating system. Microsoft knows this, just as everyone who reads this article knows this.

    --
    Be sure to remember the Programmers Prayer
  • Features by Anonymous Coward · · Score: 0

    ...with much less features than Opera.

    Indeed. I've been sorely missing the giant banner-ad "feature" that's present in the free version of Opera. I always thought I had too much screen space anyway.

    1. Re:Features by Anonymous Coward · · Score: 0

      Yeah, Opera blows away Firefox with its "features"

      I must of missed the area in Opera that has a powerful adblocker, weather updates, rss feeds in toolbar, built in ftp client, bioinformatics plugin, etc etc...

    2. Re:Features by Anonymous Coward · · Score: 0

      Well, if we're counting inane plugins, then we'll have to up the size of FF's download to include everything you listed.

      Personally, there are custom .css for adblocking, I have a far better weather bar than anything in FF, I hold that RSS is overhyped crap, built-in ftp is standard, and bioinformatics in a browser? what are you smoking?

    3. Re:Features by Anonymous Coward · · Score: 0

      Yup, I've been missing that too, ever since they started using google text ads instead. Dumbass

  • 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.
    1. Re:Hrrrmpph! by ArsonSmith · · Score: 2, Interesting

      Which begs the question "What is a standard?"

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    2. Re:Hrrrmpph! by dkellis · · Score: 1

      "Raises the question", I think you mean. "Begging the question" is somewhat fuzzy in its current usage. That said, I do agree that this does raise the question on the definition of standards.

      --
      !sig
    3. Re:Hrrrmpph! by ArsonSmith · · Score: 1

      According to wikipedia I think "begging the question" fits well. Look at how this points out a failed cicular argument shown as:

      A standard is something most eveybody uses.
      Most everybody uses Microsoft.
      Microsoft is the standard.

      The gp post is trying to say there is a diffrent standard. So this "beggs the question" what is a standard, or is the first statement of the argument really true.

      From the link:
      * p implies p
      * suppose p
      * therefore, p.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
  • Eric Meyers ComplexSpiral example by JanJoost · · Score: 2, Interesting

    I'd like to submit someone elses example page of the horrific way IE6 handles CSS2:

    http://www.meyerweb.com/eric/css/edge/complexspira l/demo.html

    It not only describes what goes wrong, but why, how and where.

    Oh: Eric: if you're reading this: Thanks! :)

    1. Re:Eric Meyers ComplexSpiral example by Anonymous Coward · · Score: 0

      Horrific? It gets the background slightly wrong. And it's CSS 1, not CSS 2.

      I'm the first to point out that Internet Explorer's support for CSS is horrific, but anybody who follows the link you've supplied will just think "what's the big deal"? Look at positioniseverything and places like that if you want to scare people.

    2. Re:Eric Meyers ComplexSpiral example by Duncan+Booth · · Score: 1

      Just for interest, anyone using IE who wants to see what that page should look like can view it at http://dean.edwards.name/IE7/compatibility/complex spiral/demo.html. It is the same page, but using Dean Edwards 'IE7' which is a set of behaviours for IE to improve its compatability.

  • Why does he care? by varun · · Score: 1

    ...the Mozilla Foundation's Firefox, Apple's Safari and Opera will increase their user share as a result.

    And he has a problem with that? I don't understand why he is "looking out" for MSFT. Wouldn't he *want* them to crash and burn?

    The only reason I could think of is that since IE commands market share, IE standards are the de facto web standards.

    Thoughts?

    1. Re:Why does he care? by SmokeHalo · · Score: 1

      Web developers everywhere would be dancing in the street if the various browsers all supported the same specs the same way. The need for extensive cross-browser testing would decrease dramatically. It's not as though he's really concerned that IE isn't living up to its full potential. Rather, if browsers were interchangeable with regard to their support and implementation of web standards, then the lives of web designers around the world would be easier. I'm no web designer, but I've puttered around a bit. I have to say that if I were a web designer, I'd be ecstatic.

      --
      I'm not good in groups. It's difficult to work in a group when you're omnipotent. - Q
    2. Re:Why does he care? by LPetrazickis · · Score: 1

      Opera's chief advantage over IE is the user experience. The interface is fast, the rendering is blazing, and the browser is light. Also, even if IE implements HTML and CSS properly, Opera is still far ahead. The latest Opera 8 beta just added native support for SVG Tiny. The final Opera 8 will again be the Mozilla-spanker Opera 7 was during the Mozilla Suite days.

      --
      Is this a sigs-optional kind of place? 'Cause I am totally down with that if you know what I mean.
    3. Re:Why does he care? by Anonymous Coward · · Score: 0

      The only thing I've actually liked about Opera 8 is the xhtml+voice support. And that's optionnal (have to go in options somewhere, enable it, download stuff...) So since hardly anyone uses it, and most users don't even dig this deep in the options, that means it won't be useful at all for this still... Otherwise, I only use Opera to make sure my sites render ok in it (for all 3 opera users there are out there). SVG support, nice too, but again, nobody uses it yet... And some Firefox builds do it natively too.

      And since it's missing all these great extensions that firefox has, it will NEVER be a Firefox/Mozilla spanker. Gimme forecastfox/foxytunes/adblock/bugmenot/web developper toolbar/checky/... on opera and then we'll see. It's better than IE, but most people prefer Firefox, and Firefox/Moz are free and have no ads either.

  • Depends on your standards. by SmallFurryCreature · · Score: 1

    You and I probably count WC3 standards. Others like the parent post probably count IE standards. See how that changes everything?

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:Depends on your standards. by Anonymous Coward · · Score: 0
      Opera chokes on the most basic of javascript / css stuff.

      Why does something as simple as this:
      onmouseover="this.className='siteslistitemover';" onmouseout="this.className='siteslistitem';"
      look like ass in opera?
  • I'm willing to bet 1 Red Hat and 1 MSFT share by WillAffleckUW · · Score: 1

    that MSFT will promise to comply and deliver something which does not comply.

    Practice makes perfect ....

    --
    -- Tigger warning: This post may contain tiggers! --
  • everything Web designers want it to by oliverthered · · Score: 1

    Make eeryone use IE5 and write the whole lot in flash.

    Why not do conformance testing against W3C standards like everyone else.

    --
    thank God the internet isn't a human right.
  • Some real CSS examples by mathmatt · · Score: 2, Interesting

    Look at this detailed analysis of how IE, Opera and Mizilla render CSS. Note that Opera and IE were both wrong at first, but Opera has adopted Mozilla's convention.

    This clearly demonstrates that the "browser war" is really a one(IE)-on-one(Firefox) battle with Opera and others simply choosing which side to mimic.

    1. Re:Some real CSS examples by Anonymous Coward · · Score: 0

      Maybe on the markup side that's true.

      However Opera has historically had the actual "features" (that nice Quick Preferences menu, tabs, mouse gestures etc) well before Mozilla. When I say features, I mean, things that set it apart from other browsers aside from the rendering engine.

      Unfortunately, from a user POV the rendering engine of any browser is going to lose to IE. Why? IE sucks, but so many pages are written and tested with it that basically everything works in IE, one or two geek sites aside.

    2. Re:Some real CSS examples by hkmwbz · · Score: 1
      Um, that "detailed analysis" is about one specific issue, and cannot be used to generalize. Also, the person who wrote it is known to be delusional and make up things as he goes along. He could have done the analysis for that specific issue, but he turned into something he can use in his own crusade against Opera.
      "This clearly demonstrates that the "browser war" is really a one(IE)-on-one(Firefox) battle with Opera and others simply choosing which side to mimic."
      This comment clearly shows that you are biased, and that you use anything, even just a single example of something, to make Mozilla look as good as possible.
      --
      Clever signature text goes here.
  • Go SlashFix by Em+Ellel · · Score: 1

    Thank you for the info - just installed SlashFix and Slashdot renders SO MUCH better now - not perfect, but at least consistant and no overlapping text.

    -Em

    --
    RelevantElephants: A Somatic WebComic...
  • Suggestion for future Opera press releases by soupdevil · · Score: 1

    The next time Opera has a blatant headline-grabbing press release ploy, they should have it sung by a fat lady in recitative style. That would get lots more attention.

    1. Re:Suggestion for future Opera press releases by SmokeHalo · · Score: 1

      That sounds like a bad Acid2 trip to me.

      --
      I'm not good in groups. It's difficult to work in a group when you're omnipotent. - Q
  • Web Designers need money too... by f0dder · · Score: 0, Offtopic

    web designers.. these the same people who use flash at every turn.

    Are paid to place 'ads' creatively in YOUR FACE.

    pfft..

    1. Re:Web Designers need money too... by redivider · · Score: 1

      Way to be coherent.

      What is it you're trying to say again?

      --
      Sinch
  • 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. :)

    1. Re:Microsoft has everything to WIN here, not lose by Anonymous Coward · · Score: 0

      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.

      While you have a point here, IF there is truly an uproar from coproprate customers for standard compliant browsers, and IE7 was completely standards compliant, then by definition they're not demanding IE specifically. And there's the rub--full standards complaince makes the web browser a commodity product, and so MS has no product differentiation to build on.

      What you're saying is that companies would prefer to stop supporting non-standards-complaint browsers so they can design once for a page that will render the same everywhere. I'd agree. But the tranisiton period would be fairly long--it will probably be 2-3 years before retiring IE5 support will really be a reality for pages facing everyday users (bank sites, mail sites, corporate sites) where the goal is to support every customer.

      Sorry, but the "phase out" of a broswer simply isn't that fast. And it certainly wouldn't be a major SALES driver! Who's going to build "IE7-only!" websites until a vast majority of users are on IE7? Not the major corporate sites you're claiming.

      And IF you're starting with the assumption that "IE7 only runs on Longhorn," then you're not going to have people building sites that are using the compelling features here UNTIL Longhorn is rolled out.

      You're confusing the cart and the horse here. People don't design major sites to assume "newest and best." The design to support "old and slow but still out there." That won't change. And the amount of design work is the same regardless of the distribution of customers across browsers.

      You get benefit when designers can assume anything older than IE7.0 is not likely to be used, and so can be unsupported. Considering most sites still support back to IE5 and Nescape 4.75, this isn't going to happen anytime soon.

    2. Re:Microsoft has everything to WIN here, not lose by Anonymous Coward · · Score: 0

      As a result, MS could very easily make IE7 only available on longhorn.

      Where have you been? This was Microsoft's plan all along, they only announced Internet Explorer 7.0 for XP last month in response to Firefox's growing market share.

      You are forgetting that every Firefox user is also running a XUL platform. XUL will be in competition with Microsoft's XAML very soon. They need to keep XUL - and by extension Firefox/Mozilla/Netscape - below critical mass.

  • Ho hum by SmokeHalo · · Score: 1

    This is as boring as a reality show.

    Next time on Survivor: W3C...
    Tension mounts as the tribes try to win the Acid2 Challenge!

    --
    I'm not good in groups. It's difficult to work in a group when you're omnipotent. - Q
  • A whole app is needed by Anonymous Coward · · Score: 0

    One page won't replicate the way IE handles MIME types (it tries to open things so you have to fake the stream), unless you write PHP or Servlets to do it all. Plus the erratic behavior it exhibits after handling downloads (http://support.microsoft.com/default.aspx?scid=kb ;en-us;306673#kb3/). Not to mention the whole list of JS bugs that have existed in IE for several versions... if IE7 is going to be good it needs to be reworked from the gound up with w3c standards in mind. Fat chance of that.

  • The Mouse That Roared by popo · · Score: 1


    And in other Headlines:

    Kwon Suk electronics throws down the Blu Ray interoperability gauntlet to Sony...

    OpenOffice.org throws down the multiple file-format compatibility gauntlet to Microsoft...

    The SVG Coalition throws down the open source scalable vector graphics gauntlet down to Macromedia...

    And..

    Belgium throws down the human-rights gauntlet to China...

    Now that we're done listening to the pitiful whines of the little guy can we get back to accepting that most things aren't fair?

    --
    ------ The best brain training is now totally free : )
  • Re:Like say the same joke everytime? by Anonymous Coward · · Score: 0

    Sorry dude, but any moron can get karma around here. Seriously, at one point I had a streak of 15 +5 posts in a row, and they were all mostly banal obvious crap.

  • Typical Opera "Soap Opera" by levitater · · Score: 1

    We should all realize this is typical Opera behavior: Make broad claims against Microsoft in order to attract attention to itself. Works well in politics and now in browser wars...

    1. Re:Typical Opera "Soap Opera" by hkmwbz · · Score: 1
      "We should all realize this is typical Opera behavior: Make broad claims against Microsoft in order to attract attention to itself. Works well in politics and now in browser wars..."
      Are broad claims about Microsoft a bad thing even when they are absolutely correct? Microsoft has, time and time again, promised, and then failed to deliver.

      If you are a Microsoft fan, you probably don't know this, but Microsoft does the same thing all the time. It's called marketing. Only Microsoft does it with FUD and lies. Opera does it with well founded criticism of the dominant browser, which fails to deliver on its promises.

      If you are a Mozilla fan, you probably don't know this either, but Mozilla, too, does marketing, and even lies about its competitors (see comment about Opera's portability).

      Don't pretend that Opera is any worse than anyone else, or that Opera's comments are without merit. Don't pretend that "this is typical Opera behavior", when the fact is that it is typical behavior from just about everyone.

      Basically, just stop being a mindless zealot, bashing Opera for nothing.

      --
      Clever signature text goes here.
  • web developers are not the issue here by meridien · · Score: 1

    Despite their inevitable protestations, web developers are NOT the arbiter of the desired behavior of browsers (any browser). The arbiter is that the browser properly renders pages according the the DTD at the top of the document - nothing more. "Proprietary" extensions to the HTML/XHTML standards should be frozen out, and properly coded pages should display consistently in all browsers purporting to meet the standards.

  • This won't help by Mozk · · Score: 1

    Even if IE gets 100% standards compliant, lots of people will still use IE 6 and lower for years to come. I'm thinking it will take at least two years before at least 50% of IE users start upgrading. So developers will still have to make ass-backwards code for them.

    --
    No existe.
  • Another Microsoft Challenge by Anonymous Coward · · Score: 0


    I challenge Bill Gates to drink a gallon
    of Draino. That's about as likely and
    much more useful.

  • Some proof that at least Microsoft is trying... by loom_weaver · · Score: 1

    They've mostly converted msn.com to xhtml strict with stylesheets. It ain't the prettiest thing but it's a step forward when it comes to web designs.

    http://www.stopdesign.com/log/2005/01/31/msn-goes- css.html/

    1. Re:Some proof that at least Microsoft is trying... by loom_weaver · · Score: 1
  • My favorite tag by Jakeypants · · Score: 1

    The tag is supported by Netscape, FireFox, and probably others but NOT Internet Explorer.

    Microsoft has ignored this important feature for years.

    1. Re:My favorite tag by Anonymous Coward · · Score: 0

      Uhg! I had forgotten all about that... I guess some good came out of Netscape's demise.

    2. Re:My favorite tag by Anonymous Coward · · Score: 0

      "The [BLINK] tag is supported by Netscape, FireFox, and probably others but NOT Internet Explorer.

      Microsoft has ignored this important feature for years."

      Thank God! What are you MS fanboi ???

  • ...you might be a standard by thegnu · · Score: 1

    I think it can definitely be defined as "a non-proprietary agreement among the members of a field"

    The whole non-proprietary thing rules Microsoft out of claiming that almost anything they do is a standard. To put it another way:

    If people don't have to pay to use you... ...you might be a standard

    If you are agreed upon by the majority of members of a community... ...you might be a standard

    If you aren't controlled and owned by a single entity... ...you might be a standard

    If you aren't used as a tool to squash competition... ...you might be a standard

    If you don't by design benefit only one party in the community, against the will of others... ...you might be a standard

    Capiche? :)

    --
    Please stop stalking me, bro.
    1. Re:...you might be a standard by Anonymous Coward · · Score: 0

      So are miles and gallons a standard?

    2. Re:...you might be a standard by thegnu · · Score: 1

      The destinction I think you might be missing about a community is that it's as big as it is. So it IS a standard, within the US. The metric system is a standard as well. If, on a global scale, the United States were to enforce lbs/mi, then you might argue against it.

      It's definitely not the World Wide standard. Microsoft, I'm sure, has internal coding standards, and I'm sure .NET follows standards. But .NET is not "a standard" on the World Wide Web.

      Catch my drift?

      Oh, and "the US government, the US population, and US corporations" is not easily analogous to "Microsoft, the company." Maybe you should pick a better footing from which to snipe, home-bot.

      --
      Please stop stalking me, bro.
    3. Re:...you might be a standard by drsquare · · Score: 1

      Says who? You personally don't define what a standard is. The de facto standard is what people use, not what some commitee decide on. It's the difference between theory and reality. Microsoft are so powerful

    4. Re:...you might be a standard by Curtman · · Score: 1

      The de facto standard is what people use, not what some commitee decide on.

      No, a de facto standard happens when people agree on a protocol without the existence of a formal standard. When the formal standard exists, (and came about with input and support from Microsoft) the other becomes known as "the wrong way".

    5. Re:...you might be a standard by drsquare · · Score: 1

      Known by who? A few irrelevent nerds who don't count? The formal standard is irrelevent if no-one uses it. And by no-one, I mean no-one who counts. When browsers totalling 51% market-share use a 'standard', then it becomes a standard. And Firefox doesn't count, it doesn't exactly follow the standards perfectly.

    6. Re:...you might be a standard by Curtman · · Score: 1

      Did you even look at the membership list of the w3c? It doesn't have anything to do with a browser having market share, and everything to do with a standards body publishing a standard.

      I said Microsoft is a member of the w3c and do not follow their standards, and you start talking about browser stats. WTF? There are actual standards, not just things that are that way because they happens to work in a particular browser.

    7. Re:...you might be a standard by drsquare · · Score: 1

      If no-one follows them they're less than irrelevent. Microsoft are bigger than the w3c, they think about the w3c standards no more than an elephant thinks about an ant. You can't just define something as a standard, people have to actually follow it.

    8. Re:...you might be a standard by Curtman · · Score: 1

      Microsoft are part of the W3C. You are a fool.

    9. Re:...you might be a standard by drsquare · · Score: 1

      Doesn't matter. Microsoft set their own standard, whether you like it or not.

    10. Re:...you might be a standard by Curtman · · Score: 1

      Yes it does matter. Think back to when this thread started. You said Microsoft's version of HTML was a de facto standard. If Microsoft is committed to the w3c, for all the reasons that they were committed back when they had the smaller market share, then they don't set a standard of any kind. It simply fails to comply with the standard.

      IE7 will hopefully bring them closer to the goal of being compliant with the standard. Bugs are not features, I don't care what the marketing dept tells you.

  • Why just [W3C] by Anonymous Coward · · Score: 0

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

    I thought some didn't like the W3C, and their "standards"?

  • 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!)

  • The problem...as I see it by msimm · · Score: 2, Interesting
    Is the web developers. I've had some down-right nasty exchanges by developers who believe that because IE represents 95% of "their target market" that 'standards' don't matter.

    A good example would be something along the lines of this (a response from an actual discussion I took part in, the funny thing was I wasn't trying to tell anyone anything about the W3C or the importance of standards, I just asked a question about a script that was acting strange in Firefox, my current platform of choice):
    A group of nameless and faceless aHoles got together and declared to the world, this is the "standard." You have to "validate" your code or it's no good, because we say so.

    And people like you, fall all over yourself, worshiping them.

    In my opinion, only a damned fool let's someone else manipulate him, whether he can see him or not.

    Those aHoles are meaningless to you, they are meaningless to your web site, but you are so weak and gullible, that you can't and will never understand that.
    Admittedly this is an extreme example, but I believe it is representative of a broader belief that might makes right. Firefox/Mozilla/Opera/Safari are still a relatively small ripple and there are some stodgy people out there who at best, simply don't care if their code works on a minority browser.

    Until it hits their pocket-books thats not going to change. The pressure needs to be put on businesses so that when say Bank AAA gets a site built that can't/doesn't support your browser (because of non-standard code created by people either too stubborn or too lazy to spend the extra 3 seconds to create/read about browser-friendly code) they hear about it. Maybe even lose some customers.

    Then our friendly web-developer can come back and learn how to fix his/her code. If that happens enough they'll get tired of doing it the old way and maybe play nice from the get-go.

    FTR, the code we were discussing in the the above quoted passaged did get fixed, by me and I have about 2 weeks of javascript programming under my belt (and if your wondering about the preceding conversation, no, I wasn't impolite or anything like that, I'm too old to pull that kind of crap).
    --
    Quack, quack.
    1. Re:The problem...as I see it by Anonymous Coward · · Score: 0

      >> because of non-standard code created by people either too stubborn or too lazy to spend the extra 3 seconds to create/read about browser-friendly code...

      God I hate this shit.

      1.) Have you ever tried to keep up on every single idiosyncracy that every browser has? There's tons. God forbid you ever have a site marginally more complex then Google's homepage. Oh yeah, and nobody ever has to maintain legacy code that a web developer wrote previous to CSS2 even existing. I'm sure that *never* happens. On a complex site (multiple pages, multiple different layouts), you have to pick your battles.

      And a previous poster had it right, you MUST support IE, which is tough enough as it is (each dropdown is it's own windowing layer? GREAT!). So don't sit there and tell me it takes three seconds to do good cross-browser design that degrades gracefully in all cases.

      What's that? You thought supporting Firefox and IE would be enough? You don't want to miss out on Opera users, or ancient Netscape users, do you? Guess what, you're code complexity just went through the roof. I hope you're not planning on a skinnable site, because then you have to maintain seperate markup and CSS for all cases too. Goody!

      2.) In your fantasy land, apparently web developers all work for themselves. Because I push at my company for IE AND Firefox compatibility (which I get my way about 5% of the time), and if I mentioned opera and netscape and Lynx and Section 508 accessibility I would get laughed at.

      That is, unless when they ask the magic question (wait for it): "How much will it cost," I can say "My hourly rate / 20".

      But I can't. Because I live in the REAL world, where a site like drudgereport.com's main page just doesn't cut the mustard.

      Cheers.

    2. Re:The problem...as I see it by msimm · · Score: 1
      I couldn't have outlined what I'm talking about better myself.

      AC, you miss the forest for the trees. Its *not* about supporting every single platform, that would simply be stupid.

      What it is about is the lowest common denominator. Like it or (in your case maybe) not, thats what standards are for.

      They push the resonsibility back on the software developers and we all know some try harder then others to play nicely.

      And I'm sure your painfully aware: you can augment your W3C compiant code (hey, its the best you should be expected to do) with and IE specific hack if need be. As in:
      <!--[if IE]>
      <style>
      .thumb {
      border: 0px solid;
      cursor: pointer;
      width: 195;
      height: 200;
      }
      </style>
      <![endif]-->
      A rather random example of something I'm sure you already know.
      --
      Quack, quack.
  • Re:Opera? Compatibility? by Anonymous Coward · · Score: 0

    That bug has been fixed in the beta they released today. But tell me, since when does a proprietary ActiveX object count for the purposes of deciding whether something is interoperable or not?

  • get SlashFix by LWATCDR · · Score: 2, Informative

    Maybe Slashdot should just put it on the front page.
    http://hardgrok.org/blog/item/slashfix-firefox-ext ension.html
    This is a firefox extension that fixes the strange rendering that Slashdot's broken html creates.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  • MOD PARENT INSIGHTFUL, NOT FUNNY by northcat · · Score: 1

    N/A

  • No incentive by bananahead · · Score: 1

    Microsoft has absolutely no incentive to participate in any kind of 'standards' testing for IE. Why should they? They own 85%+ of the browser market and the type of testing being proposed is the same as the plight of the typical IT manager: "The best you can ever be is not a bum". If they pass the standards test they are no better off than they were before. Nobody believes that the IE haters in the universe are going to change their minds because Microsoft passes this test. On the other hand, if they fail the test, they are harmed. It will never happen.

    --
    A most overlooked advantage to owning a computer is if they foul up there's no law against wacking them around a bit.
  • OMG!!@!@! by Anonymous Coward · · Score: 0

    HEHE OMG!! YOU'RE SO CLEVAR!! "APPLICATION PLATFORM. OR DIE"!!!! HEHEHEHE!!! JAJAJ Y0U ARE T3H T0PZ!!

    I can't believe you got modded up for that trite buzzword spewing bullshit wrapped in formulated follow-the-leader sentence structure, lame ass. Get some fucking creativity and original ideas.

  • hmm by mattyrobinson69 · · Score: 1

    i had a css style sheet that _crashed_ IE6 on XP/XPSP2, i had to hack it to bits to make it work.

  • Let's be honest... by suitepotato · · Score: 1

    ...the site they need it to work with is Vincent Flander's old webpagesthatsuck.com pages. We don't need more standards compliance from browsers, we need more standards compliance from web coders, the group which actually generates more WTF? responses than all the app coders at MS. Are legibility, ease of use, lack of eye strain, sensible intuitive layout, grammar, and spelling that much to ask for? If so, let's just turn over all web design by law to people who've never visisted the Internet by anything but AOL.

    Java powered buttons that jump and prevent you from clicking them, flashing backgrounds, swirling letters flying all over, embedded music forcing you to yank the freaking speakers off the machine... That's where compatibility is at right now.

    --
    If my grammar and spelling are off, I am [distracted/tired/careless] (take your pick)
  • Re:Opera? Compatibility? by Fweeky · · Score: 1

    It's a preview for a reason. And what higher standard are you holding Opera to? Firefox has plenty of bugs and misfeatures of its own, and yes, they do tend to go unfixed for a depressingly long time (up to and including never).

    Certainly in my experience as a web developer, Opera's tended to fare better than Gecko and KHTML-based browsers with regard to layout problems and incomplete standards support. Opera's hardly perfect, but it gets closer than most.

  • 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)
  • Who would ask for such a thing... by atlacatl · · Score: 1

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

    Why would anyone ask such question? If IE7 were to catter to every single designer out there, the software will be vaporware for the rest of eternity.

    A better challenge: make IE7 do everything it's supposed to do, as far a W3 standards go.

    My request: "Can IE7 prepare my breakfast, while rendering HTML? Everyday?"

    --
    Esta es una firma en Espanol.
  • Internet Explorer X .NET by cesarbremer · · Score: 1

    Do you really think Microsoft have interest in doing a better Internet Explorer?
    Microsoft need to sell Windows, and why will it improve the browser to compete against .NET?
    A better browser interface will enable using the browser as a client, and will transfer all the programming work to the server, and why Microsoft will fight in the server arena?
    Now Microsoft is selling .NET, and .NET is only a remake of the Windows API.
    The new Internet Explorer version will came because the Firefox success.

  • Re:Opera is hardly dead. by :jax: · · Score: 1
    A quick Google search reveals this Q42004 presentation that apparently shows them not doing so hot, and I think that maybe the advancement of Mozilla/Firefox has bitten into at least a small portion of their market.

    Actually Opera Software is doing well, on desktop too. The desktop revenues last year increased with 43%, and 88% year on year for Q4 2004, which was the quarter when FireFox 1.0 was released. Those are not numbers of a struggling company. In fact all browsers benefit from an awareness that there are alternatives to Internet Explorer.

  • Re:Opera? Compatibility? by fbg111 · · Score: 1

    The Opera 8 Betas (1,2, and 3) support XmlHttpRequest. I've been using them for the past few months, and they're as stable as a release browser. Can even use Gmail with them, although there are still a few layout rendering bugs there.

    --
    Flying is easy, just throw yourself at the ground and miss. -Douglas Adams
  • Automated Acceptance by Doc+Ruby · · Score: 1

    I'd love to see a browser GUI test page that was bundled with a successfully rendered bitmap, and tolerances for rendering "differences". Then much of the testing could be automated, which trial and error is usually a big chunk of GUI debugging. Which therefore usually gets blown off in favor of earlier shipping dates, at the expense of useability.

    --

    --
    make install -not war

  • Actually, now that I think about it by phorm · · Score: 1

    My current version (Linux Debian/Unstable) seems to be rendering fine lately. The version on my windows box (either 1.0 or 1.0.1) tends to be stupid about it and will crap layers over top of each other, etc... so that the article/comments text overlaps the left nav bars.

  • Re:Opera? Compatibility? by Anonymous Coward · · Score: 0
    I'm all in favor of standards compliance, but I don't see why XmlHttpRequest was foolish. Not every new tech has to be invented by standards bodies. In fact, I would argue that standards bodies aren't all that good at inventing stuff. Compare the W3C XML Schema to RELAX NG, for example.

    The IETF does it right: after there are two independent implementations, then they'll consider making a standard out of it.

  • In my case... by benhocking · · Score: 1

    I was just trying to write HTML. (This was years ago when I was first learning.) I believe one problem was when I left off </li> tags. IE correctly assumed that when I started a new <li> tag, that it should insert a </li> for me. Netscape ignored the new <li> tag since it hadn't received a </li> tag, and hence my list was not a list under Netscape. I did know enough to look at both browsers, so it isn't accurate to say that IE was the reference browser. This was not the only issue, but it captures the flavor of some of the discrepancies.

    This is not to say that what you describe doesn't happen. It's just not the only explanation.

    --
    Ben Hocking
    Need a professional organizer?
  • So, where is the w3 equivalant?? by edxwelch · · Score: 2

    There is none.
    I'm glad they made that "foolish" decision, because without XMLHTTPRequest you have no such thing as responsive web apps, no gmail, no google maps, etc.

    1. Re:So, where is the w3 equivalant?? by leighklotz · · Score: 1

      > There is none.

      Actually, there is. The W3C offering is XForms, which is indeed being implemented in Firefox. Together with CSS, it's quite powerful.

    2. Re:So, where is the w3 equivalant?? by edxwelch · · Score: 1

      Okay I stand corrected, there is a standard available... but no one has yet implemented it, which makes it fairly useless if you want to develop a web app today.
      XMLHTTPRequest has been available since 1999.

    3. Re:So, where is the w3 equivalant?? by leighklotz · · Score: 1

      > Okay I stand corrected, there is a standard available... but no one has yet implemented it.
      Actually, it has been implemented quite widely. There is an implementation about 80% done for Firefox available as a single-click 160kb install with each nightly build, a free plugin from Novell and from x-port.net for Internet Explorer, a complete open-source implementation from Finland, and a plethora of server-side transformations both proprietary and open source, plus a variety of implementations in areas other than desktop browsers.

    4. Re:So, where is the w3 equivalant?? by edxwelch · · Score: 1

      Actually, I don't think XForms is a replacement for XMLHTTPRequest at all. I read the introduction and it says it's designed as a replacement of HTML forms (as the name implys).

    5. Re:So, where is the w3 equivalant?? by leighklotz · · Score: 1

      >Actually, I don't think XForms is a replacement for XMLHTTPRequest at all. I read the introduction and it says it's designed as a replacement of HTML forms (as the name implys).
      XForms provides for loading multiple instances of XML documents (into XPath-accessible DOM trees) from URLs, customized display of the XML using form controls and display widgets, and interaction and update of the data in the XML tree with the widgets, followed by posting of XML data back to the server.

    6. Re:So, where is the w3 equivalant?? by jp10558 · · Score: 1

      I still don't get why you can't just use a Java applet. Or moreso, why you want web apps in the first place.

      --
      Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
    7. Re:So, where is the w3 equivalant?? by hkmwbz · · Score: 1
      "I'm glad they made that "foolish" decision, because without XMLHTTPRequest you have no such thing as responsive web apps, no gmail, no google maps, etc."
      Sure you would. Just use the standards compliant variant, DOM3 Load and Save, which Opera 8 supports.
      --
      Clever signature text goes here.
    8. Re:So, where is the w3 equivalant?? by edxwelch · · Score: 1

      Yes, isn't that what I said? XForms is form related stuff and not specificaly a replacement to XMLHTTPRequest.

      Maybe you could somehow hack it so that a non-form based application such as gmail would use the methods to pass data, but this may not be a pretty solution.

    9. Re:So, where is the w3 equivalant?? by leighklotz · · Score: 1

      > Yes, isn't that what I said? XForms is form related stuff and not specificaly a replacement to XMLHTTPRequest.
      Somehow we are talking past each other. XMLHTTPRequest loads XML data into an area accessible to JavaScript and other DOM client code in the browser. The XForms instance object is the same thing.

      I took a look at the IPod RSS feed example, and it's a bit of a hack. The example has tons of JavaScript in it, and it doesn't actually parse the RSS feed, or at least not much of it. It gets the titles out, but then all it does is use the .innerHTML method to display HTML content that is escaped as CDATA inside the RSS feed. It's not much cleaner than using a frame to do the same thing.

      I'll try to write an XForms version of the same thing, that works on the RSS feed from Apple. But I need to wait for a few more features to reach completion in the Mozilla XForms implementation.

  • Of course there is incentive by TubeSteak · · Score: 1
    If MS manages to pull it off, their PR people will undoubtly tout IE7 as being 100% standards compliant.

    I can already picture the ad campaign:
    "Now you'll see the Internet the way it was meant to be seen."
    Or some other touchy-feely marketing speak.

    and don't forget, its not a bug, its a feature

    --
    [Fuck Beta]
    o0t!
    1. Re:Of course there is incentive by bananahead · · Score: 1

      I disagree. Microsoft doesn't look at the world that way. A zero-sum game is not in their best interest. They do not have any interest in testing that would serve to level the playing field in any way, which is all this would. It won't happen.

      --
      A most overlooked advantage to owning a computer is if they foul up there's no law against wacking them around a bit.
    2. Re:Of course there is incentive by TubeSteak · · Score: 1
      Zero-Sum?

      there will always be new buyers and users entering the computer market every day.

      MS might have noticed that its not just the /. nerds using firefox/zill/opera anymore, but that its slowly spreading to the non-technical user.

      Even MS is smart enough to realize that if you can please the uber nerds, they won't tell their parents to switch to another browser.

      --
      [Fuck Beta]
      o0t!
  • Opera's dead? Better tell Adobe and Macromedia by bonch · · Score: 1

    Seeing as how Dreamweaver and GoLive use Opera's engine for their web development apps, and all those mobile devices and general users who run Opera every day, it's hard to believe anybody on Slashdot (which is rabidly pro-Firefox no matter what) when there are comments like "Opera is dead" that actually get modded up.

    Opera has long been one of the better and faster browsers. Not only does it take up half the memory of Firefox, but it takes up half the file size.

  • Aunt Sally says "No Way" by dghcasp · · Score: 1
    If you think Microsoft is going to fix currently buggy things in IE, I think you're deluding yourself.

    To explain this, I'll use the infamous "Aunt Sally" test; Aunt Sally downloads a new version of IE that meets all standards. Then she finds out that half of her favourite web sites don't look right because they were coding to IE bugs.

    Question: Who will Aunt Sally blame? She won't blame the site, because she doesn't even know what HTML is, let alone CSS. She'll blame Microsoft for putting out a bad browser and revert to the old version.

    If you iteratively apply the Aunt Sally test, and thus have hundreds of thousands of Aunt Sally's with the same problem, what will the media do? Well, they'll put together news stories that say IE7 is not working yet and tell people not to download it.

    And what's the end result for Microsoft? It spent mega-$$$ on upgrading IE7, and the only people that like it are those whiny Linux users, who don't use Microsoft products anyways.

    So what do you really think MS will do?

    1. Re:Aunt Sally says "No Way" by convolvatron · · Score: 1

      actually given the state of things i think Aunt Sally would blame the site for not working with
      her 'perfectly normal' computer. it seems thats how we got here in the first place.

    2. Re:Aunt Sally says "No Way" by vonsneerderhooten · · Score: 1

      Aunt sally will find another site that offers what she's looking for, and works with her browser. Other Aunt Sally's will do the same. Said site will evolve, or perish.

      Darwinism at its finest.

  • acid challenge by west.to.east · · Score: 1

    I'm up for the challenge unrelated, embedded Flash suchs

    1. Re:acid challenge by west.to.east · · Score: 1

      yes I should have used the Preview button..
      unrelated, embedded Flash suchs

  • Re:Opera? Compatibility? by Finuvir · · Score: 1

    XmlHttpRequest is part of the in-development Web Hypertext Applications Technology Working Group (WHAT-WG) Web Forms 2 (aka HTML5) standard, which will be submitted to a number of standards bodies when it's ready. WHAT-WG has members from Opera, MoFo, and Apple. All of those organisations have committed to implementing it.

    --
    Why is anything anything?
  • Web Interoperability by scdeimos · · Score: 1
    From the linked article:
    Microsoft now has the chance to redeem itself with regard to Web interoperability. All it needs to do is make sure IE7 passes the Acid2 test before shipping.

    I might point out that the majority of users are obviously *NOT* concerned with interoperability or they wouldn't be using MS-IE in the first place.

    Whilst I think interoperability is good (and I don't use MS-IE, except for that danged Add/Remove Programs applet) people need to realize that it's the Web Developers who are making the most noise about interoperability, and unfortunately, the Web Developers are in the community minority.

    One could argue that MS isn't likely to pay attention to the minority purely from a Business/Economics point of view. (ie: it costs them money to satisfy "developer whims" on a free/bundled product.) Perhaps they'll start to pay attention once their marketshare gets eroded by Firefox and other browsers. :)

    *crosses fingers*

  • Ughh... by Anonymous Coward · · Score: 0

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

    I would settle for IE doing what it's supposed to do per specifications (ie. CSS).

  • Re:Opera's dead? Better tell Adobe and Macromedia by Anonymous Coward · · Score: 0

    Slashdot is "pro-" a lot of things, but being pro-firefox is normal, everybody seems to be like that, not just slashdot. Opera might be one of the best, but it's no better than firefox (doesn't even come close imho) and it cost money or you have ads. Oh, and filesize IS completely irrelevant nowadays, and memory wise, I've never seen it be an issue on any PC I've tried it onto. It works well, fast, lots of features and all. I have yet to see anyone (other than on /.) say they prefer opera over it. No, I don't think apple stuff is really this good at all, no I never really cared for iPods, no, I don't think linux/foss is the solution to everything nor all that like too many ppl say here, but opera is in NO WAY AT ALL WHATSOEVER better than Firefox, not even close.

  • This is much easier than it sounds by mr_burns · · Score: 1

    My shop supports IE, Moz and khtml engines and only w3c dom. We test on multiple platforms. Generally during a build the pages work in all derivitave browsers in all platforms except bugs that pop up in IE, which we later fix.

    If anybody else is in the same boat all we have to do is save that version of a site that works in everything except IE and submit it. No need to create a special version.

    --
    "Let him go, Ralph. He knows what he's doing." --Otto Mann (simpsons)
  • They don't... by Razzak · · Score: 1

    Opera just hadn't been in a /. story for a while.

  • Re:Like say the same joke everytime? by cbr2702 · · Score: 2, Funny

    Perhaps you mean ad nominum attacks?

    --


    This post written under Gentoo-linux with an SCO IP license.
  • Ugly Sentence by vosbert · · Score: 1
    "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."


    Am I the only one who thinks this is an ugly and confusing sentence unfit for a slashdot headline?

  • Re:Like say the same joke everytime? by Anonymous Coward · · Score: 0

    Why don;t you set your reading level to more than 0 then, can;t figure out where the pref page is?

  • What market are you operating in? by Chuck+Chunder · · Score: 1
    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.
    That's just laughable...
    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
  • "The Critic" on Government: It Stinks! by Anonymous Coward · · Score: 0

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

    So when are we going to get "Government 2.0"?

    1. Re:"The Critic" on Government: It Stinks! by SpecBear · · Score: 1

      You make a legitimate point. There are quite a few parallels.

      We have not yet reached the point where anyone besides the political analog of hard core geeks is attempting to switch. Few people are leaving the country to flee the government, few are joinging militias or even actively participating in advocating alternatives to the current government policies.

      I sat around bitching about IE for some time before I made the switch to Mozilla. I only recently started actively evaluating Linux for use on my desktop machine. As far as government is concerned, we're still in the stage where the lots of people are just bitching about it, but very few are taking action.

  • Winfrey? by spacemky · · Score: 1

    Oprah Lays Down Acid2

    Wow. I've been staring at this screen just a little too long.

    --
    640YB ought to be enough for anybody.
  • Re:Opera? Compatibility? by leshert · · Score: 1

    It's a preview for a reason. And what higher standard are you holding Opera to?

    The reason for the "higher standard" is that I don't recall anyone from the top ranks of the Firefox developers pulling a PR stunt like Opera's.

    Don't get me wrong: I like Opera the browser. I even shelled out for it a few years ago. But try to see a spade for a spade.

  • Both by setmajer · · Score: 1

    As I recall, both tables *and* frames were Netscape extensions. And don't forget the all-singing, all-dancing layer and ilayer tags (ugh). And then there's applet, embed, non-tag stuff like the layers collection, JSSS (JavaScript Style Sheets), even JavaScript (nee LiveScript) itself.

    You could maybe count the img tag too, which was implemented Andreeson while everyone else was haggling over details of the much more useful object tag.

    Netscape did a lot to push the web forward, but they made a hella mess while doing so. Historically, Microsoft was much more standards-friendly. Heck, the authors of the first Acid Test refused to even test Navigator/Communicator 4.x because its CSS support was so gawdawful poor the list of things that needed fixing was virtually indistinguishable from 'everything'.

    --

  • Ya, Opera's HTC implementation is really cool by setmajer · · Score: 1

    Nothing like overstatement to answer overstatement, yes?

    Microsoft added some things that are getting implemented by other browsers, but very often they're being implemented for compatibility with IE-only sites, not because they were such good ideas. The document.all collection, for example.

    Other things are truly useful (offsetFoo -- Height, Width, etc. -- for example), and others are convenience features that don't really do much that couldn't be accomplished via W3C-recommendation-compliant methods like .innerHTML*.

    Still others were on a par with the worst of Netscapes excesses (marquee anyone?).

    There are also plenty of areas where Microsoft went off on their own path and nobody followed (conditional comments, behaviors, CSS expressions) or abused the W3C recommendations with incompatible and/or incomplete implementations (e.g. the object tag, esp. their, ah, 'interesting' use of the codebase attribute).

    * Maybe not the best example, as at least some tests indicate that in most all browsers that support it .innerHTML is much faster in terms of rendering time than the corresponding W3C DOM methods.

    --

  • Opera DOES have problems by setmajer · · Score: 1

    So does Firefox, and the current development version of the Acid2 Test exposes at least some of them (I'm on the dev list for the test and have seen it).

    --

  • NETFRONT?! Reality check... by Anonymous Coward · · Score: 0

    Netfront is supposed to kick Opera's butt?

    Hahaha... Hilarious. Netfront is trying hard to catch up with Opera, but will never be able to because Opera started out as a real web browser, while Netfront started out as a lame WAP/mobile browser without proper support for normal web sites.

    Access (creators of Netfront) are scared shitless of Opera. They even ripped off Opera's help files!

  • The Acid2 test is NOT Opera's baby by setmajer · · Score: 1

    It's sponsored by the Web Standards Project, just as the original Acid Test was.

    A couple of Opera people ARE doing a lot of the work on the test, but the current dev version exposes Opera bugs as well (I'm on the dev list and have seen it).

    I can't speak for either the WaSP as a group or the other folks involved in the test, but I can assure you I have no interest in contributing to something that's just an Opera PR stunt. This is intended to reveal weaknesses in ALL browsers. The challenge to MS is a result of their inaction/indifference since IE6 (itself rather half-hearted in terms of improved standards support, save for the 'fixed' box model), not because they're the only ones not getting the standards right.

    --

  • Re:Opera? Compatibility? by hkmwbz · · Score: 1

    Or you could just use the standards compliant way to do XMLHttpRequest, namely DOM3 Load and Save.

    --
    Clever signature text goes here.
  • I'm sorry, but..... by HogynCymraeg · · Score: 1

    why the hell would you care?

  • Useful? by tepples · · Score: 2, Interesting

    However, the CSS and XHTML specs on the W3C site are difficult to understand and therefore not all that useful when you're trying to debug a rendering problem. In addition, which browsers support searching the specs for, say, all rules that contribute to this border?

  • Opera and Javascript by Anonymous Coward · · Score: 0

    I know this is all fine and wonderful that Opera can throw gauntlets at Microsoft and call them out on their lack of CSS support. But what about Opera and it's horrible broken implementation of javascript? ..

  • Standardize -> Implement -> Deploy by tepples · · Score: 2, Informative

    edxwelch's comment, take 3: There is a standard available (XForms), but no one has yet deployed it.

  • 795499 by mnemonic_ · · Score: 1

    Son, talk to me when you have a 200000 user number. Until then, shove it.

    1. Re:795499 by Bander · · Score: 1

      Using your user number to trump someone else seems childish at best, compensatory at worst.

    2. Re:795499 by Ohreally_factor · · Score: 1

      You'd talk to me in a mirror universe.

      --
      It's not offtopic, dumbass. It's orthogonal.
  • They used to by bluGill · · Score: 1

    Remember back when everyone, even companies had a best viewed with netscape link on their page.

    Netscape always sucked. I never could stand it, but for years everyone was telling me I had to use it.

  • I tried acid once and the pages looked great by SimonInOz · · Score: 1

    Lots of colour and movement .... pretty ...

    --
    "Cats like plain crisps"
  • Welcome to Slashdot by gosand · · Score: 1
    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.

    You just described the Slashdot moderation system.

    --

    My beliefs do not require that you agree with them.

  • Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  • Re:Standardize - Implement - Deploy by leighklotz · · Score: 1

    >edxwelch's comment, take 3: There is a standard available (XForms), but no one has yet deployed it.
    Yes, that's mostly true. It's been published, it's been implemented, but it hasn't been widely depolyed. There are deployments, but widespread deployment will depend on widespread implementation. I'd be satisfied with implementation in Firefox, and move on from there.

  • Dude! by Grendel+Drago · · Score: 1

    Just a little heads-up here---that's a chick.

    Happy to help, my friend.

    --grendel drago

    --
    Laws do not persuade just because they threaten. --Seneca
  • CSS Ease by csaba2000 · · Score: 1
    The way I see it, widespread conversion to the type of CSS usage envisioned by CSS evangelizers won't happen until it becomes easy to do the things that people are used to doing without CSS, such as with tables. If your CSS is larger OR more complicated than the tables what have you gained?

    Here's an example of how to position a block (table cell) of fixed width and height, in any of 9 relative positions within the doc, and then to have content similarly positionable. It's very easy to alter the alignments (positioning). This kind of thing can be simulated using CSS but each position requires special "hackery" and winds up being complicated to switch between (and not even considering IE here).

    Now, I agree that the structure below (two levels of tables!) is far from desireable, but it's quick and it works. Now you would think that you could create a div (or something) and put its style to display:table-cell and remove at least one level of table. I'd love to see it work. This is simple basic stuff that people need - unless CSS offers it, developers will be staying in table land.

    A second example I saw today. Someone had an input element (of type text) in a table cell they wanted to expand to the full width of the cell (because they had several such in the same column and this was a simple way of producing uniform width). This did not work because the margin extends past the box! IE may have gotten the box model wrong, but there were some things that were much cleaner with it. The point is that reasonable types of things should be easy to do - that's what will gain mass acceptance.

    Csaba Gabor from Vienna
    <html><head><title>Table cell test</title></head>
    <body style="margin:0" noscroll bgcolor=green><table
    style="height:100%;width:100 %"><tr>
    <td style="height:100%;width:100%" valign=bottom align=center><table>
    <tr><td valign=middle align=right style="height:4in;width:5in;background:pink"
    >Thi s text goes to the middle right<br>of a bottom left div<br><br>
    How to do it without tables???</td>
    </tr></table></td></tr></table></b ody></html>