Slashdot Mirror


W3C Says IE9 Is Currently the Most HTML5 Compatible Browser

GIL_Dude writes "The W3C posted results for their latest HTML5 compatibility tests and have found that, so far, IE 9 has the best overall results. 'The tests cover seven aspects of the spec: "attributes," "audio," "video," "canvas," "getElementsByClassName," "foreigncontent," and "xhtml5." The tests do not yet cover web workers, the file API, local storage, or other aspects of the spec. Not do they cover CSS or other standards that have nothing to do with HTML5 but are somehow lumped under HTML5 by the likes of Apple, Google, and Microsoft.'"

60 of 382 comments (clear)

  1. Posting from IE8... by anss123 · · Score: 5, Interesting

    Does slashdot work any better in IE9?

    1. Re:Posting from IE8... by Anonymous Coward · · Score: 5, Funny

      Slashdot works differently horrible in all browsers.

    2. Re:Posting from IE8... by electron+sponge · · Score: 5, Funny

      No, I'm still seeing the same stupid comments

    3. Re:Posting from IE8... by bmo · · Score: 2, Insightful

      There's a "brightness" knob on my TV, but that never seems to work either.

      --
      BMO

    4. Re:Posting from IE8... by Byzantine · · Score: 5, Funny

      Consistency is all I ask

    5. Re:Posting from IE8... by bluefoxlucid · · Score: 2, Funny

      Ask the other poster about his "brightness" knob.

    6. Re:Posting from IE8... by Saishuuheiki · · Score: 5, Funny

      Will consistency in inconsistency suffice?

      Or consistently inconsistent

    7. Re:Posting from IE8... by WrongSizeGlass · · Score: 5, Insightful

      Or doesn't work properly if you have JS disabled since they removed or disabled the old comment controls. In a similar vein, the W3C test results are presented via some javascript crud. Assuming that is that the visitor has it enabled.

      A lot of website functionality is built with JavaScript - that's just a fact of life. You don't have to enable it, but you really can't complain when websites don't cater to the small minority of users who either disable or block all scripts. We're trying to get sites not to support the dying number of IE6 users, and I'd be willing to bet the % of users not using JS is even lower than IE6 users. If all sites were simply written in HTML there would be a lot less 'web' out there.

    8. Re:Posting from IE8... by jedidiah · · Score: 2, Insightful

      The list of scripts present in a random website is positively scary. It's little wonder that Windows users always get infected with some nonsense. There's no way for a webmaster to control and manage all of the external dependencies present in the sites created by the "screw the minority" crowd.

      It's like medical outsourcing out of country where your medical history becomes subject to hijacking or auction.

      Every external dependency is another place for management, security and responsibility to fail.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    9. Re:Posting from IE8... by Jah-Wren+Ryel · · Score: 2, Insightful

      A lot of website functionality is built with JavaScript - that's just a fact of life. You don't have to enable it, but you really can't complain when websites don't cater to the small minority of users who either disable or block all scripts.

      But you can damn will complain when javascript is used unnecessarily, especially when it's used as a crutch by obviously lazy and/or neophyte developers because their laziness results in their users being unnecessarily exposed to increased security risks. Nobody disables javascript because they want to, they disable it because javascript is the number one source of web browser vulnerabilities by at least an order of magnitude, probably two.

      Web developers are (supposed to be) the experts, web users are regular joes -- it should be the experts that bear the burden of making websites that encourage good security practices, rather than putting the burden on the non-experts to have to deal with increasing array of vulnerabilities.

      If all sites were simply written in HTML there would be a lot less 'web' out there.

      I disagree. There would be a lot less crap, and probably only slightly less useful content. But above all there would be a hell of a lot less malicious websites and compromised ad networks.

      --
      When information is power, privacy is freedom.
    10. Re:Posting from IE8... by pjt33 · · Score: 4, Insightful

      I think the Anonymous Coward has a stronger case here. Graceful degradation is the way sites are supposed to work. You can't complain when the snazzy stuff doesn't work with JS turned off, but you can complain when basic forms don't work.

    11. Re:Posting from IE8... by EvanED · · Score: 5, Insightful

      Nobody disables javascript because they want to, they disable it because javascript is the number one source of web browser vulnerabilities by at least an order of magnitude, probably two.

      No it isn't, not even close. Flash and Acrobat Reader are by far the biggest infection vectors; raw, browser-based JS is positively benign by comparison.

      Stuff like making it easier to do tracking cookies and be generally annoying are JS's biggest flaws.

    12. Re:Posting from IE8... by omfgnosis · · Score: 2, Interesting

      I know it's a petty nitpick, but hear me out. There's a reason the more intelligent among front-end web developers ditched the term "graceful degradation" for "progressive enhancement". For all but a minuscule (but growing) portion of possible web tasks, the client-side approach has a direct HTML/HTTP/server-side analog with—if we're doing our jobs right on the client-side—a UI that is less usable and slower. Even though the two philosophies could be implemented the same way, they rarely are. The philosophy of "graceful degradation" is essentially that the UI is the application and its core functionality is an afterthought to be implemented as a fallback; the philosophy of "progressive enhancement" is essentially that the core functionality is the core responsibility, and that client-side behavior is meant to improve the user experience. Another difference between the philosophies is that, where the analogs exist between client-side and traditional functionality, "graceful degradation" tends to carry with it an implication of increased development cost, whereas "progressive enhancement" promotes a model that allows simplified development. (Again, note that I am not discussing the terminology so much as existing differences in approach.)

      I think, though, there's a line to be drawn between content delivery and applications, in terms of the responsibility of web developers. I don't think that information on the Internet should be hidden behind a wall like requiring Javascript; but I do think that some of the capabilities of web-based applications don't have a direct analog to HTML/HTTP/server, or can't be implemented that way in a reasonably acceptable way. As an example, web-based video can definitely be implemented without client-side scripting; but web-based video editing cannot (within users' perfectly reasonable expectations). You might say that this latter category ought not be implemented in the browser in the first place, but for better or worse you're fighting a trend that's probably not going to die any time soon.

  2. Not suprising by metrix007 · · Score: 5, Funny

    For all the flak IE gets, it's actually a great browser. We all know Microsoft make great products and often take the lead when forced to, and now is no different.

    It is also the most secure browser by far, what with its inherent use of MAC, and full DEP and ALSR support. Strange, but true.

    --
    If you ignore ACs because they are anonymous - you're an idiot.
    1. Re:Not suprising by Anonymous Coward · · Score: 2, Interesting

      No kidding - place I work has to block Chrome, Safari, and Firefox at the firewall since all three have actively exploited zero-day exploits.

      But not IE8. It's secure.

      And, yes, they also block all versions of IE prior to 8, because those also have actively exploited holes in them, but if there's one thing Microsoft did right in Vista, it's securing IE. Too bad no other browser maker takes advantages of the OS features used to do that.

    2. Re:Not suprising by WrongSizeGlass · · Score: 4, Interesting

      IE 9 is currently the most HTML5 compatible browser - but are they only testing the new HTML5 features? How does it do on the HTML4 code that is currently 99% of all the code on the internet?

    3. Re:Not suprising by OzPeter · · Score: 2, Interesting

      For all the flak IE gets, it's actually a great browser..

      I don't mind IE at all, and use FF daily too. However I much prefer the text rendering of Safari on both PC and Mac

      --
      I am Slashdot. Are you Slashdot as well?
    4. Re:Not suprising by BenoitRen · · Score: 2, Funny

      Steve Ballmer, is that you?

    5. Re:Not suprising by Yvan256 · · Score: 4, Interesting

      No other browser is limited to Windows.

    6. Re:Not suprising by makomk · · Score: 3, Informative

      Not only that, but I think at least one of the features they're testing is a former IE-ism that's been standardised, and the other browsers have prioritized HTML5 features like local storage that aren't tested here at all.

    7. Re:Not suprising by TheRaven64 · · Score: 4, Informative

      On Snow Leopard, yes. FireFox uses the platform's native text rendering engine. Safari uses Apple's one wherever it runs. This means that you get Apple's sub-pixel AA instead of Microsoft's ClearType on Windows.

      You also get some slightly different glyph positioning. Microsoft tweaks glyph positions by a fraction of a pixel to make them line up more closely with pixel boundaries. This makes individual characters clearer, but means that the spacing between characters looks a bit messed up. Apple renders glyphs exactly where they should be, which means that they often overlap pixel boundaries and need a lot of antialiasing.

      If you're used to Microsoft's rendering, Apple's text will look slightly blurry. If you're used to Apple's rendering, Microsoft's will look weirdly spaced.

      --
      I am TheRaven on Soylent News
    8. Re:Not suprising by God'sDuck · · Score: 3, Informative

      That's probably because Firefox supports fractional font sizes: 12.1px, 12.3px, 12.5px...
       
      Every other lunkheaded browser rounds to the nearest whole pixel value. If the site developers use relative font sizes (ems, percents) and don't do precise math, the site ends up with a declared pixel size between values...and only Firefox delivers the declared size.
       
      As a CSS guy, this means I find other browsers infuriating. Now that we have Webfonts I want to render ever piece of text with fonts instead of graphics...but getting a banner to just the right size is often impossible without a fractional font size. As a normal user, it means Firefox more often than not looks "wrong," because it's far enough ahead of the curve to be out front alone.

    9. Re:Not suprising by mugurel · · Score: 2, Funny

      No kidding - place I work has to block Chrome, Safari, and Firefox at the firewall since all three have actively exploited zero-day exploits.

      But not IE8. It's secure.

      and just in case it's not, there's always lynx for windows ;-)

    10. Re:Not suprising by Purity+Of+Essence · · Score: 4, Insightful

      Well, how about this: Limited to Windows 7 / Vista. That's a much bigger problem for the 50% of us who use Windows XP.

      --
      +0 Meh
    11. Re:Not suprising by Purity+Of+Essence · · Score: 2, Insightful

      It's a lot easier to just not use IE9.

      --
      +0 Meh
    12. Re:Not suprising by bonch · · Score: 2, Interesting

      They're also comparing a development version of a browser to the released versions of other browsers, instead of their development versions. For example, Chromium already passes tests that Chrome failed in the article.

    13. Re:Not suprising by fast+turtle · · Score: 2, Insightful

      As a user, I find any site specifying any font size to be infuriating as they tend to not display properly with my settings. A damn good example of that is /. itself. I've had to push the font size in Firefox to 16pts as the minimum, just to get a readable size on screen. It's the same for many websites and that violates the entire spirit of HTML, which was basic formating yet all of a sudden we're seeing so many sites use damn screwy fonts and sizes just to be different.

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    14. Re:Not suprising by DragonWriter · · Score: 2, Interesting

      IE 9 is currently the most HTML5 compatible browser - but are they only testing the new HTML5 features?

      From the coverage of the tests, they seem to be pretty close to the features that were tested in Microsoft's own compliance tests, which were then submitted to the W3C for inclusion in the W3Cs test suite.

      To highlight this: see here.

      Notice that the only directory here is "Microsoft"?

    15. Re:Not suprising by CAIMLAS · · Score: 2, Informative

      If you're used to Microsoft's rendering, Apple's text will look slightly blurry. If you're used to Apple's rendering, Microsoft's will look weirdly spaced.

      As a Linux user, Apple fonts look blurry; Microsoft fonts (AA'd or not) look like jagged crags of ugly (very difficult to read, at times - see the powershell font).

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    16. Re:Not suprising by hairyfeet · · Score: 2, Interesting

      Actually you can blame that on good old Ballmer. I had lots of friends on hacked XP and they are all running w7 now, Why? Because of the $50 HP upgrade, that's why. Ballmer really shot them in the foot when he pulled the $50 HP upgrade, as there are a ton of late model Athlons and P4s that will be running XP until EOL simply because at the current price it is better to invest in a RAM upgrade than an OS one. I myself have a nice Sempron 1.8GHz with 1.5Gb of RAM I use for a netbox. It is quiet, compact, uses very little power, and makes a great box for web surfing and downloading. At $50 I probably would have gone ahead and upgraded it, but at $90 it is simply a better investment to get a new Radeon AGP GPU and max out the RAM at 2Gb than it is to buy W7 for it. And don't even get me started on Vista, or as we in the shops call it "WinME: The sequel".

      So whether you and Ballmer like it or not XP is "good enough" just like those millions of late model P4s are good enough for what most folks use them for. Ballmer could have used that $50 HP upgrade as a foot in the door to not only gain share back for things like IE and Windows Live, but it would have also gave him a captive market to try to upsell to Pro. Instead he shot himself and his company straight in the foot. That is why I still think the Gate Borg on /. should be replaced by a Ballmer in a beanie with his tongue out wearing an "I Heart Apple!" T-shirt, as that seems to be the current state of management.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    17. Re:Not suprising by shutdown+-p+now · · Score: 4, Interesting

      As a CSS guy, this means I find other browsers infuriating. Now that we have Webfonts I want to render ever piece of text with fonts instead of graphics...but getting a banner to just the right size is often impossible without a fractional font size. As a normal user ...

      As a normal user, I do not want you to have the ability to define exact pixel sizes of fonts, without my ability to override them without completely breaking site layout (which is what will happen if your buttons etc will be designed for a specific size). There are many reasons for why that is the case, but the most obvious one is that I do not want to see tiny, hard-to-read text, and so all my browsers are set up to not allow anything below 13px. Any well-designed website works fine with such an arrangement; if yours does not, I will just go elsewhere.

      By the way, one of my personal dislikes with Flash is that there is no way to impose a similar restriction there, and that Flash designers, for some reason, love tiny fonts for menus, buttons and such.

    18. Re:Not suprising by shutdown+-p+now · · Score: 4, Informative

      Safari uses Apple's one wherever it runs. This means that you get Apple's sub-pixel AA instead of Microsoft's ClearType on Windows.

      This used to be the case, but for a while now Safari for Windows gives you the choice between OS stock rendering, and Apple's fonts.

      Microsoft tweaks glyph positions by a fraction of a pixel to make them line up more closely with pixel boundaries. This makes individual characters clearer, but means that the spacing between characters looks a bit messed up. Apple renders glyphs exactly where they should be, which means that they often overlap pixel boundaries and need a lot of antialiasing.

      To be more specific, ClearType tweaks glyphs such that vertical lines are snapped to pixel boundaries - so a 1px vertical line is rendered using a single-pixel-wide column of physical pixels. On OS X, the same 1px vertical line can end up on fractional coordinates (e.g. at X=8.5px), and will be rendered using double-pixel-wide column of physical pixels to approximate that. The result is more blurry.

      This is particularly noticeable on small fonts with thin elements, such as Windows system fonts Tahoma 8pt (in 2K/XP) and Segoe 9pt (in Vista/7). It's also why OS X default font is larger, and the stems are thicker.

      The disadvantage with ClearType approach is not just "weird spacing", though. It distorts the overall size of the text by its adjustments. Normally, if you increase the point size twice, the physical size in pixels should also increase by exact same amount (+/-1px due to need to round to physical pixel boundary). OS X rendering actually guarantees that. On Windows, text rendered using small fonts is noticeably (by 20% or so) larger than it would be if "perfect rendering" was used, and so proportion is not maintained.

      Which one is better is highly subjective, and more often than not the preference is defined by what the person was using before. Personally, I can't stand OS X rendering and love ClearType. I've met people who felt just as strong in the other direction.

    19. Re:Not suprising by shutdown+-p+now · · Score: 2, Informative

      It's all a bit complicated. Let me try to explain.

      First of all, VS2010 does indeed use WPF 4, though not for all UI elements (it was not a grounds-up rewrite). But text editor is fully WPF, and so are menus and toolbars. Tool windows may or may not be on a case-by-case basis.

      WPF 4, unlike previous versions, does use DirectWrite when available. This is indeed the same technology that IE uses, and it provides for "perfect rendering", where font glyphs are not snapped to vertical pixel boundaries, and therefore proper text size is maintained without distortion. It should be noted, though, that even past WPF versions used the same kind of rendering, though they had their own text layout engine.

      Now, DirectWrite actually has a flag which disables "perfect rendering" and enables pixel-snapping for fonts, with the result being not pixel-by-pixel identical to the traditional GDI ClearType, but pretty close to it. WPF 4 exposes it as a property on all widgets.

      VS2010 beta 2 actually used the "perfect" rendering, and there were a lot of user complaints about text being blurry etc. This MS Connect ticket (which I had created, though the problem was reported long before on various forums and blogs) summarizes the issue Consequently, WPF added the aforementioned property, and it was used from VS2010 RC to enable ClearType-style rendering for all windows in the application.

      From what I've seen in IE9 beta, they use DirectWrite, but they do not use that same flag. So their rendering is different from what you see in VS2010, and specifically more blurry. I wonder if they'll end up going through the same change by the time they release - I've actually suggested that they do so.

    20. Re:Not suprising by shutdown+-p+now · · Score: 3, Insightful

      Having access to a 14.5px font has absolutely nothing to do with using 8px font.

      GP was complaining about the inability to use fractional-sized fonts in general, and his explanation as to why he needs it is so that he can precision-match text on various UI elements. My point is that his expectation of being able to precision-match text size at all is incompatible with basic accessibility issues, and that any website relying on such tricks is broken for many people.

      It doesn't have anything to do with specific font sizes. Mine's minimum is set to 13px because that's what I can read well without squinting on my display. My mother's vision is much worse, so hers is at around 15px or so (I don't recall exactly), so even in a browser which supports fractional font sizes, a webpage requesting 14.5px would not get it.

    21. Re:Not suprising by IICV · · Score: 2, Funny

      My theory is that a large proportion of Flash "designers" are 13 years old and are "designing" on either some hand-me-down computer that's only capable of running at 800x600, max, or Dad's old work laptop that runs at 1024x800.

    22. Re:Not suprising by willy_me · · Score: 4, Informative

      If you want pixel perfect rendering of fonts and graphics, use PDF or a related technology. The whole idea behind HTML is that the content can be rendered differently on different devices. As such, a proper design should never rely on exact font sizes.

    23. Re:Not suprising by omfgnosis · · Score: 2, Interesting

      the official claim was that IE8 fully supports CSS 2.1

      Unfortunately, the other official claim at the time was that IE prioritizes interoperability over standards compliance, and the two claims together did not jibe. I've encountered far too many instances where IE 8 was correct and the competitors were correct also, except the standard allowed for differences of interpretation and IE 8 alone took different interpretations.

      Moreover, IE 8's biggest gaping hole was not its HTML or CSS support, nor even some of its oddities in ECMAScript, but its utterly disfigured DOM implementation, largely unchanged from IE 6 (if not earlier). There are so many analogous-but-slightly-different IEisms in the DOM that huge general-purpose libraries are necessary for most developers to do anything useful on the client-side that isn't missing core features in one implementation or the other.

      I haven't seen much from MS about IE 9's DOM improvements, and I'm kind of scared to find out if it's still being hung out to dry. My hope is that, while their public projection of "HTML5" is far too broad to be meaningful, their internal priority does include true HTML5 compliance, which will standardize the DOM.

  3. Well I'm going to say congrats... by catbutt · · Score: 4, Interesting

    ....to Microsoft, for moving in the right direction of adopting standards. I still hate you, Microsoft, but I hate you less.

    Now figure out a way to get people to stop using IE6. (maybe an add-on to IE9 that makes it so you can run your ancient IE6 only apps?)

    1. Re:Well I'm going to say congrats... by Anonymous Coward · · Score: 2, Interesting

      It does support quite a bit of the css3 draft including rounded corner, box shadows, etc..

      I find it funny that IE (from 7+) seems to have the best implementation of @font-face

    2. Re:Well I'm going to say congrats... by cababunga · · Score: 2, Funny

      Now figure out a way to get people to stop using IE6. (maybe an add-on to IE9 that makes it so you can run your ancient IE6 only apps?)

      Yeah... Maybe they should ask Google to write an IE6-frame for them, or something.

    3. Re:Well I'm going to say congrats... by cbhacking · · Score: 2, Informative

      Um no, it really doesn't "remain to be seen" at all. The very first preview of IE9 (10 months ago, now) had CSS rounded corners, for example.

      You could always try out the tests on http://ie.microsoft.com/testdrive/Default.html in your browser of choice. They all work on IE9, and usually better (faster, smoother, or without layout issues) than on other browsers. All browsers, even IE8, can do some of the stuff there, but all other browsers have issues with some parts.

      That's not to say IE9 doesn't still have issues with soem things that other browsers do fine, because it does. For example, I don't think it has WebSockets. However, it's still not only a huge step up from earlier versions, it's also better than its competitors in many areas.

      --
      There's no place I could be, since I've found Serenity...
  4. I feel conflicted by zill · · Score: 2, Funny

    On one hand, Microsoft managed to produce an excellent product that's almost fully compatible with the latest standards.

    On the other hand, they're the same people who's responsible for summoning the Devil's own child into this world (under the trademark of IE6).

    I honestly don't know what to feel about them right now.

    1. Re:I feel conflicted by Anonymous Coward · · Score: 2, Insightful

      Its easy to look back at IE6 and say "holy crap what a wreck!" but IE6 happened because the standards weren't moving fast enough. There is a reason IE6 took so much ground, because it actually did what people wanted. Then years later people come in with how it should have been done and now IE6 is the devil. I mean, yeah, its a pain in the ass and unfortunate, but its not like we didn't get anything out of the deal.

  5. What kind of a "standard" is this? by cowtamer · · Score: 3, Funny

    Perhaps my understanding of "standard" is a bit skewed, but isn't there something wrong when the best that a browser in its 9th version backed by the most powerful software company in the world can do is just be the "most compatible" one out there?

    All FTP clients I use are 100% compatible with the FTP standard. I believe Adobe Flash player is 100% compatible with Flash. I think most mail clients are 100% IMAP and POP3 compatible.

    Shouldn't standards be straightforward enough so that all parties wishing to comply to them simply can? Shouldn't compatibility with a standard be a floor instead of a ceiling to asymptotically crept towards?

    I'm sure I'm missing something here -- what is it?

    1. Re:What kind of a "standard" is this? by Ryanrule · · Score: 2, Interesting

      the problem is people using standards while they are still being defined.

    2. Re:What kind of a "standard" is this? by Shados · · Score: 4, Informative

      Thats why it used to be referred to as a recommendation, instead of standard (lots of discussions around it, though i think the likes of ISO and whatsnot now consider W3C stuff as actual standards).

      That said, if you ever tried to implement anything from the W3C, its full of holes, inconsistencies, ambiguous parts, things "left to the implementator", and all around, Microsoft's OOXML may have been a lousy ISO standard, but it sure would fit right in anything the W3C ever published.

      The only reason it kindda works, and that so many browsers seem to implement it, is because the likes of those working on Firefox, Safari, etc, kind of agree on stuff they don't like or the standard doesn't dictate. That also makes IE8 look worse than it actually is (not that its not awful, but in a few (very few) cases web developers will complain about things on which IE8 is actually right, and Firefox is wrong, but Safari, and Chrome are wrong the same way).

      Its not just HTML/CSS/whatever. The XQuery specs for example, are just as bad.

    3. Re:What kind of a "standard" is this? by WrongSizeGlass · · Score: 3, Funny

      I'm sure I'm missing something here -- what is it?

      If it makes you feel any better IE 9 is 100% Microsoft compatible ... the most Microsoft compatible browser under development.

    4. Re:What kind of a "standard" is this? by Jahf · · Score: 2, Insightful

      Technically ... neither is IE9. This article seems to fail in pointing out that it just compared a browser still in the preview phase to other browsers that are released. The board will keep changing, the difference is that within a few months of IE9 coming out there will be new Firefox and Chrome releases. The further difference here being that a year or two after IE9 coming out those same browsers (and likely Webkit/Safari, Opera, etc) will all have multiple releases.

      So IE9 has essentially caught up ... so what? Microsoft was dragged kicking and screaming to the point of being the "most compliant" and once it reaches that goal it will end up touting that marker well after the other browsers eclipse it.

      --
      It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
    5. Re:What kind of a "standard" is this? by Jahf · · Score: 3, Insightful

      What an awful example. FTP is a nearly completely static protocol with no defined presentation layer for user interaction. On the other hand HTML5 is not even a completed standard yet and is almost entirely focused around creating user interactivity with the data.

      What you are missing is this ... FTP doesn't correlate to HTML5. FTP correlates to HTTP. HTML5 would correlate more with the concept of the GUI to utilize FTP. Of which there are MANY completely different examples, none of which work perfectly for all situations. If you want to compare FTP to something regarding the web, then make comments about how well your web browser complies with the ability to communicate with a web server. In which case pretty much all browsers will be compliant.

      --
      It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
    6. Re:What kind of a "standard" is this? by maxwell+demon · · Score: 5, Informative

      Technically ... neither is IE9. This article seems to fail in pointing out that it just compared a browser still in the preview phase to other browsers that are released.

      The "released" browsers are:

      Google Chrome 7.0.517.41 beta
      Firefox 4 Beta 6
      Opera 11.00 alpha (build 1029)
      Safari Version 5.0.2 (6533.18.5)

      The only one which doesn't have "beta" or even "alpha" in its name is Safari. So probably that one is actually released.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    7. Re:What kind of a "standard" is this? by afidel · · Score: 2, Informative

      Did you try disabling the Win7 firewall rules? My guess is the client does active FTP and that is where the problem is.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    8. Re:What kind of a "standard" is this? by Dr.Dubious+DDQ · · Score: 2, Insightful

      Well, since the alternative is to wait another half-decade for W3C's glacial pace to finally (maybe) get to a finished standard, I think most people prefer to start in on it now, rather than continue being stuck on the now decade-old HTML4.01/XHTML 1.1 combo.

  6. And let's ignore that big fat '0' by Slutticus · · Score: 2, Funny

    in the foreigncontent row

  7. My first suspicion by snsh · · Score: 3, Interesting

    Did Microsoft just manage to pull an OpenOfficeXML with the HTML5 standard?

  8. Tried with latest chromium by HelloKitty2 · · Score: 3, Interesting

    Just tried with latest chromium, it passwed all random tests I clicked on, that the tested chrome failed on.

  9. Re:Irrelevant by Bigjeff5 · · Score: 2, Insightful

    Apparently you weren't paying attention when IE6 became IE7, nor when IE7 became IE8, and you're certainly not paying attention now when IE8 is about to become IE9.

    Microsoft is obviously continually improving their product. If they weren't, this article would not exist.

    They are not, however, doing it on the schedule you would like them to do it on, and for some reason in your mind that qualifies as stagnation. Most reasonable people can recognize that this is, in fact, a major improvement in a long line of major improvements, which obviously discredits your claim completely.

    --
    Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
  10. Some of tests seem dumb, and site seems broken. by clone53421 · · Score: 2, Interesting

    I stopped clicking through the tests one-by-one when I came across one that would have been fixed by a simple “if (x1 == x2 && y1 == y2) return;”. I went ahead and scrolled down the list, though... for some reason a lot of the tests near the bottom read “No Result” for many/most browsers, and clicking a test at random (canvas(2d.transformation.scale..zero.html)) that said “No Result” in every column except Safari gave me a 404 error.

    I’m not terribly impressed.

    --
    Alexander Peter Kristopeit bought his basement from his mommy for one dollar.
  11. Embrace comes before Extend by erroneus · · Score: 2, Insightful

    It's all part of their standard operating procedures after all. If they wish to get back on top, they will need to support the standards... then, of course, they will extend on them, get developers to use the extensions and then make sure everyone else looks "broken" again. Seen it all before.

  12. The test is vastly incomplete... by Dreadrik · · Score: 5, Interesting

    ...according to the test developers.

    According to wired:

    Run IE9 against other aspects of HTML5 and the browser would be decidedly behind its competitors. IE9 lacks support for Web Workers, drag-and-drop features, SVG animations and the File API, all of which are vital components for building useful web applications, and all of which enjoy considerable support in other browsers.

  13. +/- tolerances by Anonymous Coward · · Score: 4, Insightful

    As a CSS guy, this means I find other browsers infuriating. Now that we have Webfonts I want to render ever piece of text with fonts instead of graphics...but getting a banner to just the right size is often impossible without a fractional font size. As a normal user, it means Firefox more often than not looks "wrong," because it's far enough ahead of the curve to be out front alone.

    This is the web, not desktop publishing. If you want pixel perfect rendering 100% of the time generate a PDF or PostScript file (or Flash). While CSS has certainly improved the visuals, the sites I like the best are ones that actually still useful when I use lynx/elinks to visit them (e.g., Daring Fireball, Ars Technica).

    While I'm a fan of good design, you have the wrong mind set when creating a site if you want the above IMHO. Even in engineering physical things there, are some +/- tolerances; you need to have some "give" in your designs and I think it's true with HTML as well. All of this advanced CSS is nice, but after a certain point you're into the realm of "control freak" designers.

    Please remember: web site != desktop publishing. If your layout can't handle a few pixel offset here or there, then it's veered into the realm of "control freak" country.