Tuesday, March 4, 2008 1:07:54 PM
It looks like Microsoft has changed its mind regarding standards in IE8
We've decided that IE8 will, by default, interpret web content in the most standards compliant way it can. This decision is a change from what we've posted previously.
This clearly shows how important it is to keep up the pressure
on Microsoft to finally deliver on its promises.
Some may be wondering if this changes anything about Opera's antitrust complaint, but the bottom line is that the massive focus on open standards lately might be bearing fruit. If Microsoft does deliver a browser which is standards compliant by default, this is great news indeed! And at least now, we will have the EU keeping an eye on Microsoft, and giving it real incentive to follow up its promises for once.
Monday, February 25, 2008 9:41:17 AM
Microsoft's mantra for IE8 basically being IE7 (or not using the new standards compliant mode) by default is "don't break the Web"
. It is interesting, then, that Microsoft does exactly that with the new useragent string for IE8
Wednesday, January 23, 2008 8:32:49 PM
In his blog, Jeffrey Zeldman defends version targeting
. As most people probably know by now, there is a proposal out there which involves IE8 basically requiring that you opt-in to its standards compliance. Needless to say, most people think this is a really
, really bad idea
. Apart from Zeldman's attempt at dismissing criticism as "ingrained dislike of Microsoft", something else really caught my eye.
Thursday, December 20, 2007 6:30:19 PM
If you take the Acid2 test
in any browser, you will notice that they all fail. This is not because all browsers suddenly stopped passing Acid2, but because of an error with the test itself.
Wednesday, December 19, 2007 11:26:58 PM
The IEBlog announced today (or is that yesterday by now?) that internal IE8 builds
now pass the Acid2 test
This is certainly a promising development in these times of antitrust complaints and "wars" over standards. Acid2 only tests a smaller portion of certain standards, so it will be interesting to see the first public release of IE8 and how far along it is when it comes to open standards.
In any case, congratulations to the IE team, and I hope this is only a tiny first step in the process of turning IE into a standards compliant browser.
Our Web Opener, David, has written a longer piece with his thoughts on this interesting development
. Needless to say, he's a happy camper.
Tuesday, December 18, 2007 2:52:17 PM
Important note: In this blog, I speak on behalf of myself and myself alone. I am not involved in W3C activities at Opera, as my work is mainly outside the area of standards. For official statements from Opera Software ASA, please get in touch with our PR contacts or read our press releases. With that out of the way...
I have previously written about how there are signs that Microsoft may be trying to sabotage the EcmaScript 4 standard
by using various dishonest tactics, such as misinformation and stalling. Imagine my surprise when, even at a time when it is under investigation for anti-competitive practices
, Microsoft may be actively working to slow down the progress of other standards as well.
Sunday, December 16, 2007 4:02:44 PM
While I personally think focusing on enforcing standards alone would be the best solution in an ideal world, there is still a strong case for unbundling IE.
Friday, December 14, 2007 3:36:52 PM
Two days ago, Opera Software filed an antitrust complaint with the EU against Microsoft
(please note that this is not
a lawsuit). You have probably read about it by now, because it has been all over the Web (and then some).
Reading some of the discussions on this subject, I have noticed a lot of questions being asked, and many assumptions about Opera's position and motives for doing this. I know that we are going to be giving out more details as time goes by, but I thought that I would post some thoughts on the issue, from the perspective of someone inside the Opera organization.
One thing that has surprised me is the seemingly one-sided focus on one of the two proposed remedies, namely the unbundling of MSIE. People seem to forget about the second proposed remedy - forcing Microsoft to adhere to Web standards, which is even more important in my opinion. The first is just a way to prevent Microsoft from having the power to continue its practices. Both are about giving people an actual choice.
Anyway, here is my small "FAQ" based on some questions and issues I've seen raised around the Web.