Slashdot Mirror
Update on Standards and CSS in IE7
brajesh writes "Chris Wilson has posted on IEBlog about the Standards and CSS in IE7. According to the post, "In IE7, we will fix as many of the worst bugs that web developers hit as we can, and we will add the critical most-requested features from the standards as well. Though you won't see (most of) these until Beta 2". Further,"we will not pass this (Acid2 browse) test when IE7 ships.""
Although there will be Microsoft bashing in this thread, I believe this is good for all browsers because almost all the other browsers are standards compliant. Therefore, as IE becomes more standard compliant, the common denominator between the browsers will be bigger thus more web pages will be displayed correctly in all the other browers. I appauld Microsoft for this effort although it might be a result of necessity rather than goodwill. ;)
Why? Because they ARE the standard and they know it. In a perfect world, they would conform to the standards that everyone else is striving to hit. But MS knows they own the market. They know that there are a bazillion web pages written specifically for IE. They know there are lazy coders out there that don't bother checking for web standard conformity and only care that their pages work on IE. So why should they rethink their IE development? It's much easier this way (for them). It's a shame, and maybe some day it'll kick 'em in the ass, but for now, they know they're in the driver's seat.
"He uses statistics as a drunken man uses lampposts...for support rather than illumination." - Andrew Lang
Simple. M$ isn't going to concede that they can't keep up; not even to technologies they don't even have yet. They will buy technology, mimick it, or simply continue to bastardize. The thought, "You know, this software from Acme is filling the niche well. There's no reason for us to go into that segment" never occurs to them. Let alone, "You know, we've wrestled with standards and security and perhaps we should exit the browser market given the great alternatives out there." They want it all and they want it now.
This was with reference to CSS standards and web development, not exploitable vulnerabilities in the browser's security.
My 3D Texturing Skinning work (under construction)
Let's go over a few logical fundamentals:
Your post should be marked as a troll. You haven't got a clue what you're talking about.
To be honest, ACID2 isn't that important - it tests some extreme corner cases in CSS usage. If you are 100% CSS compliant then it should work, but if you are 80% compliant then there are more important things to implement than passing ACID2.
I am TheRaven on Soylent News
Now, open IE up and look at the Acid2 test. IE completely fucks it up beyond recognition. I could render the picture better by shitting out paint.
I'm curious to know how other browsers like Opera and Safari handle the Acid2 test. Are there technically any browsers out there that can pass it?
... I was waiting for someone to point out the fact that no real browsers pass acid2. And lord knows firefox not only crashes on me once every week or two, and chews up ungodly ammounts of ram, and doesn't garbage collect in a timely manner.
Thank you Firefox! Without competitive pressure from Firefox, I doubt that we would be seeing such effort to fix longstanding issues with Internet Explorer. IE 7 won't be perfect, but it will likely be a lot better than it would have been if the Mozilla project and Firefox had never existed. I suppose in some small way this is a bit of revenge from the grave for Netscape.
To the making of books there is no end, so let's get started
Funny how quickly the MS bashing begins, yet when I just tried the Acid2 test with Firefox (my browser of choice btw), the results were far from impressive. And correct me if I'm wrong, but as far as I know Acid2 isn't an officially accepted standard, it's a *proposed* standard.
Acid2 is a test of the CSS standard, not the standard itself. And no, Firefox doesn't pass. But the Firefox team has made it a goal TO pass, unlike the IE team which has apparently said, "screw it, we're not going to waste our time just to pass that." IE is shooting for "good enough."
Considering the amount of money Microsoft could theoretically pump into development on the next version of IE, wouldn't it make more sense for them to be the first to pass the test (and by doing so provide implied compliance with the standard)?
Opera Acid2 as of today and the forum post accompanying the attachment:
Good news for Opera users.
(/snip)
So I think that sums most of 'em.
And look, if IE6 fails miserably the ACID2 test, i'm really hoping we'll see a yellow blurb at least in IE7 (right now it's like a red wall with some pieces of slaughtered yellow-face in there).
In firefox we don't see the face, but at least we can see a nice yellow thing with wierd not-intended-to-be sunglasses on... kinda.
So I'm quite curious how the ACID2 will render in IE7...
From the about page of the Acid2 browser test site:-
Note: some 827 people (rough estimate, contents may have settled during shipping) have written to point out that the CSS used in the test is invalid. This is deliberate, as a means of exposing the ability of user agents to handle invalid CSS properly.
This is why I never used things like the box model "hack" or any other browser bug-dependent CSS for cross browser compatibility. It's begging to have the site start blowing up in users' faces as soon as a new browser is released.
Even the terrible implementation of CSS in IE6 is usable enough to make sites to standard. Sure it requires a bit of cheesiness, but I'd rather do that than *depend* on their browser continuing to not only have bugs, but to react to those bugs the same in every new release.
There is a middle "standard".
vk.
Using any other browser would be running all that browser code without admin privs. Yeah, they're making a "broker" that handles all the system interface. Pretty much the architecture most unix-based server programs have been using for years. Except at the client/browser level it's unnecessary... unless you're building on previous poor design decisions.
The anti-phishing... yet another thing others have already been doing quite well for quite a while.
It's plainly obvious they're playing catch-up on many fronts. That alone isn't a reason to bash them, as least as far as I'm concerned. But calling "innovative" the features that have been implemented for over a year or more in other browsers or as third party add-ons is pretty cheap.
Or did I miss some new features, anything really, that's truely innovative in IE7, rather than just implementing features already available from competitors and third parties?
PJRC: Electronic Projects, 8051 Microcontroller Tools
From the look of it you don't code at all.
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
"But I'm still right here, giving blood and keeping faith. And I'm still right here."