Does IE8 Really Pass Acid2? [Updated] 174
thevirtualcat found some inconsistencies in IE8's Acid2 results that made him wonder what's going on. Can anyone replicate these results or, better yet, explain them?
Update: 03/22 23:54 GMT by KD : Several readers pointed out this has to do with cross-site scripting prevention, as described here.
Update: 03/22 23:54 GMT by KD : Several readers pointed out this has to do with cross-site scripting prevention, as described here.
Re:The answer... (Score:5, Insightful)
In a word, no.
Next anti-Microsoft flame, please?
This is not a security problem, per se. (Score:4, Insightful)
The fact that the blog writer mentions security is a red herring. While it is true that this does have something to do with security code, the real problem is that the fallback behavior is poor.
Simple stuff like CSS (Score:1, Insightful)
But even the most basic CSS like
margin-left: auto;
margin-right: auto;
to center a DIV doesn't work in IE8 while it works great in Firefox.
Maybe I just read the wrong HTML/CSS tutorial sites but it would be nice if they rendered things consistently.
Re:I smell bullshit at the IE blog (Score:2, Insightful)
Also, it was not an excuse, it is a reasonable security measure. Frankly, most web developers are far too reckless about security. Rule #1 of secure programming: be as paranoid as you can, and then be more paranoid. If you don't think that every user is out to get you, then you're not being paranoid enough.
You obviously didn't comprehend what you read.
Re:On another note... Acid3 (Score:4, Insightful)
Microsoft Has Lost The Race (Score:3, Insightful)
Internet Explorer is losing ground to Firefox, so they come out with a new version and claim that it meets standards and works better. Nope, it's just more of their marketing spin.
The real problem is that Microsoft has lost sight of the goal. They're supposed to be producing software that meets the needs and desires of their customers, but they're busily producing software that's only intended to further their goal of "world domination". Their marketing department is busy trying to make that pig look like a swan, but it's not working.
Too bad that Linux distributions aren't quite "there" yet - close, but not yet. This is a golden opportunity for a real competitor...
Re:Cross-domain == cross-site (Score:2, Insightful)
Please... don't use an expression that you don't understand.
Re:Yes, that's true. (Score:5, Insightful)
Acid3 isn't a standard, it's a set of tests for specifications that have already existed for years. Acid3 didn't make Firefox less compliant, it merely pointed out ways in which Firefox was already non-compliant.
Re:Simple stuff like CSS (Score:1, Insightful)
Re:It's a massive improvement... (Score:2, Insightful)
What the fuck? Yeah, I know I'd gain at least 3 hours per week in productivity if Office used a standard XML format than its current implementation.
Re:The answer... (Score:5, Insightful)
and
Re:It's a massive improvement... (Score:4, Insightful)
I'm an IT manager by trade. I don't care who provides my company with software or what platform it runs on, as long as the business I provide IT for benefits from it and it is cost-effective, ideally giving me an advantage over my company's own competitors. The changes in UI between MS Office XP (which they're mostly using now), 2003 and especially 2007 are big enough that I have to retrain my users to use them, and frankly the cost of training my users to use 2007 is enough that I've been seriously considering moving them to OpenOffice.org.
However, the lack of a properly standardized file format prevents me from doing that. I have experimented with OOo with some of my users, and the biggest complaint (once I have trained them up a bit in OOo) I have is that
I know from experience with KOffice that I get better import - pretty much spot-on for the fairly complex documents my users create - from that into OO.org as ODF than I do Word documents into OO.org, so there must be something good about having a properly standardized file format. My conclusion therefore is that if MS Office had to support ODF, then MS would be forced to fix the bugs in Word and Excel rather than rely on their proprietary file format to keep competitors out and ignore the problems.
This is a similar situation with IE8 finally fixing long-standing bugs in order to pass the Acid 2 test, which is only possible by HTML and CSS being properly standardized.