Microsoft: IE 8 to support standards from the start
Aiming to demonstrate that its commitment to interoperability goes beyond fancy statements, Microsoft said Monday that it is shifting its plans for the next version of Internet Explorer to make the program more friendly to Web standards.
The software maker said that a planned standards compatibility mode will now be the default rendering engine when IE 8 makes its debut. Microsoft has already said that the new browser is capable of passing the Acid2 rendering test.
"We think that acting in accordance with principles is important, and IE 8's default is a demonstration of the interoperability principles in action," IE general manager Dean Hachamovitch said in a blog posting.
With IE 8, Microsoft plans to have three rendering modes: the new standards-compliant mode, the IE7 rendering engine, as well as an option for displaying older Web sites. Because of the default shift, Web sites that want IE 8 to use its IE7 engine will have to add a tag to their site's code.
Microsoft noted that there are some legal reasons for changing course. "While we do not believe there are currently any legal requirements that would dictate which rendering mode must be chosen as the default for a given browser, this step clearly removes this question as a potential legal and regulatory issue," Microsoft General Counsel Brad Smith said in a statement.
At the end of last year, Opera complained to the European Commission about Microsoft's browser practices, and last week Microsoft was handed a record fine for its past noncompliance with EU dictates.
Microsoft hasn't said when the final version will be out, but a beta version of the browser is due out in the first half of the year. There also will likely be more browser news later this week, when Hachamovitch gives a keynote speech at the Mix '08 conference in Las Vegas.
During her years at CNET News, Ina Fried has changed beats several times, changed genders once, and covered both of the Pirates of Silicon Valley. These days, most of her attention is focused on Microsoft. E-mail Ina. 
"If FF/Safari/Opera already render it well, so should IE8 so most
sites won't be affected."
The problem is that lots of sites only render well in IE6-7!
So, the designer/programmer should do one of two things in
each page:
1) Put the compliance label to be rendered by IE6-7;
2) Rebuild the site to be Standards-compliant...
"With IE8, Microsoft plans to have three rendering modes: the new
standards-compliant mode, the IE7 rendering engine, as well as
an option for displaying older Web sites."
It's next best move would be... to directly use WebKit as the
Standards-compliant engine!
All problems solved!
IE8 can do whatever.
That would be the true meaning of "commitment".
If you were committed, the original plans would be committed. They are not, ipso facto, you are not.
It is a word which the executive committees have obviously not held a meeting to go over. It would be good to review in the postmortem, since the word committee is itself related to this concept.
Perhaps if you view "standards" as a way to advance computing and the industry, rather than as a way to get a wrestling hold on everyone involved, you would be better able to "commit" MS.
http://www.scorepoll.com/story.php?title=Does_Internet_Explorers_compliance_with_standards_make_any_difference
Lets send a message to Microsoft that they are on the right road, but lets get security, plugins and customization to match Firefox before expecting to prevent more attrition.
Bring back the NSAPI set!
Until then, it's all just market-speak.
(and wasn't there a lot of hype about IE7 supposedly being fully standards-compliant before it came out as well?)
/P
http://www.youtube.com/watch?v=BoSkc6zPtLQ
No there were guys like you ******** about how it WAS NOT going to be standards compliant. Thanks for showing your baseless bias once again Penguinisto.
*Insert foot in mouth now Penguin
Don't hold your breath on this one either.
To: CNTUS.PRCS.NA.00.EN.TRA.BGL.CS.T01.CUS.00.WB @ css.one.microsoft.com
Subject: Internet Explorer 7 text sizing bug/incompatibility
Message:
Both website developers AND internet software developers should consider the users of their products when creating them. However, if a web developer stumbles with regards to this, it is NOT acceptable for software developers to use that as an excuse for their own shortcomings.
Microsoft has faltered with regards to customer service and product quality expected from the company. While many people are working on "web standards", it is not reasonable to expect such standards to come into widespread effect in short order. It will take some time.
Until then, however, consumers should not be "punished" by developers who seem to want to force standards into effect prematurely. Until then, developers should accommodate consumers with regards to "Ease of Access" (to use some Microsoft terminology).
While there is more than one area where web and software developers have faltered, I am writing simply about one aspect of Internet Explorer 7 that Microsoft has failed to make work "properly" with regards to user-friendliness. (Whatever happened to that concept, anyway?)
IE7's text size feature (which should allow users to resize website text from smaller to medium to larger) does not work with website text sized using pixel-sizing.
Pixel-sizing has been used online for a long time. While some developers are currently attempting to set new standards which would make pixel-sizing obsolete (whether that is for better or worse is up to debate), pixel-sized text is still widely in use across the internet.
However, rather than make the internet experience for consumers truly enjoyable, Microsoft has seemingly decided that new web standards being forced into use is a more important goal.
Getting to the point, IE7 is not able to resize text sized using pixels. This is UNACCEPTABLE, and I request - nay, DEMAND - that Microsoft fix this problem with their internet browser. And, yes, this is a problem - a "bug", if you will. This is not an irrelevant or extraneous "quirk" that can be simply passed off to other developers and/or the consumers themselves.
If a multi-billion dollar company with the reputation of Microsoft can not fix this "oversight", then I don't know what the future holds with regards to the internet truly becoming a part of everyday life for people all around the world.
Christopher J. Carlson
Anyhoo...
I'm no MS fanboy, but IE 7 does support text resizing for page text set in pixels.
Can you site some examples of sites where pixel resizing doesn't work?
Now if only MS would fix the Outlook 2007 HTML standards train-wreck. That program was a giant step backwards for standards compliance.
Robert
Sure! The computer will fire up and start loading web pages before the installation of the OS. Not only that, but it won't even need an internet connection. The entire internet will be cached into the installation with a virtual updater which will allow you to browse news, sports, even weather generated from statistical analysis of backward compatible web pages. The menu's that used to say "please wait" are now replaced with the latest updates on Paris Hilton. Instead of configuring hardware, the virtual updater will configure all the best porn sites directly into your favorites. Once the process is complete, you press the new "STOP" button on the taskbar to log in (ctrl-alt-del is now new and improved to shut down the computer like it did in DOS). In the tips and tricks, you'll discover how to move up the system clock to a future date and get the scoop on which stocks will be the best investments.
How's that for an answer?
Later of course, they got so much market share that they successfully polluted many web standards also. But I wonder if that was a deliberate act or just shoddy programming.
The JVM concept was an obvious threat to Windows, but web standards don't seem to be. If IE8 really is standards compliant, I don't see how it would hurt Microsoft at this point. In fact, it might help IE lose less ground.
Lets see if the pig passes when it is released officially.
Of course, as long as it supports crap like ActiveX it is only a massive security hole and not worth using.
(just out of curiousity)
/P
IE8 beta almost passed Acid2 (had a couple of mis-aligned pixels), but the corp. proxy may have interfered with it.
Here's the stats on Acid 3 (which has been publicly testable since January, but official since yesterday):
Official Releases:
==================
* IE7 (current patch) on Win2k3/SP2: 12/100 (yes, "Twelve")
* Safari Mobile (on co-worker's iPhone): 39/100
* Firefox 2.0.0.11 on Fedora Core 8 Linux: 50/100
* (...does anyone have OSX 10.5 to test Safari there?)
The betas
(comfirmed also from multiple sources):
======================
* IE8 on Win2k3/SP2 (3/6/08): 17/100 (yes, "Seventeen").
* Firefox 3: 68/100
* Safari/Webkit on OSX 10.3.9 (3/5/08): 90/100
So, a note to the rabid Microsoft (and other) fanboys out there - you don't have a whole lot to brag about yet, kids. ;)
/P
Also wanted to mention that Opera 9.25 showed a 46 on the test.
True, that msft doesn't have a ton to brag about...but I think it is a
good, if belated, start.
BTW, "Windows fanbois" don't brag. They just defend against the extremely biased comments the Linux and Apple fanbois make and try and help them re-integrate with reality by making them face it.
Microsoft has given in and is running with standards compliant.
Penguinisto complains.
I don't get it, what does it take to make you happy? Get over it, you won. They are following the very standards you demaneded. And now you're complaining about it?
Dude, seriously, get over yourself. Even when MS does *exactly* what you demanded, you complain about it.
Makes me seriously consider where your paycheck is coming from. You obviously have something more than a general interest in this. Hmm.
- why this is important
- by gp2792 March 6, 2008 5:20 PM PST
- a little math based on some previous posts and 10 seconds of research.
- Like this Reply to this comment
-
(100 Comments)assumptions:
75% of the market runs IEx where x = 5,6, or 7
The remaining 25% runs a standards compliant browser - read acid 2 pass.
1 year from IE8 release, 40% adoption is reached. It took IE7 about 1 year to become the dominant IE browser, but I'll leave 10% for older versions
results if IE8 RTM passes acid 2:
(.75 * .4) + .25 = .55
meaning that in 1 year, the # of in use browsers that support basic standards will go from 25% to 55%. Is it nirvana? no...but doubling in one year would be a great improvement.
I agree that we would be much better off if ie8 supported the standards that acid 3 tests for. Let's hope that ms makes that the goal before launch.