Language Selection

English French German Italian Portuguese Spanish

Next Explorer to fail Acid test

Filed under
Microsoft

Microsoft's new Internet Explorer 7 browser won't pass a stringent standards test that rivals have embraced.

In its browser blog, Microsoft acknowledged that IE 7 would not pass the Web Standards Project's Acid2 test, which examines a browser's support for W3C (World Wide Web Consortium) recommendations including CSS1 (Cascading Style Sheets), HTML4 and PNG (Portable Network Graphics).

"We will not pass this test when IE7 ships," Chris Wilson, lead program manager for the Web platform in IE, wrote in the IE blog. "We fully recognize that IE is behind the game today in CSS support. We've dug through the Acid2 test and analyzed IE's problems with the test in some great detail, and we've made sure the bugs and features are on our list--however, there are some fairly large and difficult features to implement, and they will not all sort to the top of the stack in IE7."

Standards advocates and Web developers have criticized Microsoft for letting Internet Explorer go without a significant upgrade for years. This spring it became clear that Microsoft would finally address long-standing standards-compliance issues in its planned version 7 upgrade.

Microsoft last week came out with a test, or "beta" version, of its Windows Vista operating system and IE 7.

Wilson said the broad range of Acid2's demands made it more of a "wish list" than a "compliance test."

"As a wish list, it is really important and useful to my team, but it isn't even intended, in my understanding, as our priority list for IE7," Wilson wrote.

The Web Standards Project responded positively to the announcement, hailing Microsoft's standards to-do list and its openness in acknowledging the test.

"While it doesn't hit everything we might like, and we won't see most of it until Beta 2, it's a pretty impressive list for a release that by all accounts is primarily about security and UI features," Web Standards Project member Chris Kaminski wrote. "Even more impressive than the contents of the list, though, is that it's even available outside the Redmond campus. Having been through this 'work with Microsoft' thing once before in the late '90s, I can assure you this sort of openness is a radical departure from the Microsoft of old and as good a reason as any for optimism that this is just the beginning, and we can expect even more and better in IE 7.5 and beyond."

The Web Standards Project launched seven years ago to goad Microsoft and Netscape into heeding W3C recommendations. These days, the group takes a less confrontational approach than it used to, working closely with software companies like Macromedia and Microsoft before products are released.

Microsoft's competitors sounded a less forgiving note in responding to the news.

"I think they should take the time required to do this right," said Hakon Lie, chief technology officer of Opera Software in Oslo, Norway, who threw down the Acid2 gauntlet to Microsoft in a News.com column this spring. "We're not going to see another IE for another several years, and this is their chance to show that they really care about standards, as they've been saying. They've used so many years to create IE 7, they can take the extra month required to make it pass."

Lie said Opera was "very close" to passing Acid2. Apple Computer has already said that its Safari browser passes the test in preliminary builds. The Mozilla Foundation said it was committed to "full support" of Acid2 in its Firefox browser but did not say when it expected to pass the test.

By Paul Festa
cnet.com

More in Tux Machines

ownCloud Desktop Client 2.2.4 Released with Updated Dolphin Plugin, Bug Fixes

ownCloud is still alive and kicking, and they've recently released a new maintenance update of the ownCloud Desktop Client, version 2.2.4, bringing some much-needed improvements and patching various annoying issues. Read more

Early Benchmarks Of The Linux 4.9 DRM-Next Radeon/AMDGPU Drivers

While Linux 4.9 will not officially open for development until next week, the DRM-Next code is ready to roll with all major feature work having been committed by the different open-source Direct Rendering Manager drivers. In this article is some preliminary testing of this DRM-Next code as of 29 September when testing various AMD GPUs with the Radeon and AMDGPU DRM drivers. Linux 4.9 does bring compile-time-offered experimental support for the AMD Southern Islands GCN 1.0 hardware on AMDGPU, but that isn't the focus of this article. A follow-up comparison is being done with GCN 1.0/1.1 experimental support enabled to see the Radeon vs. AMDGPU performance difference on that hardware. For today's testing was a Radeon R7 370 to look at the Radeon DRM performance and for AMDGPU testing was the Radeon R9 285, R9 Fury, and RX 480. Benchmarks were done from the Linux 4.8 Git and Linux DRM-Next kernels as of 29 September. Read more

How to Effectively and Efficiently Edit Configuration Files in Linux

Every Linux administrator has to eventually (and manually) edit a configuration file. Whether you are setting up a web server, configuring a service to connect to a database, tweaking a bash script, or troubleshooting a network connection, you cannot avoid a dive deep into the heart of one or more configuration files. To some, the prospect of manually editing configuration files is akin to a nightmare. Wading through what seems like countless lines of options and comments can put you on the fast track for hair and sanity loss. Which, of course, isn’t true. In fact, most Linux administrators enjoy a good debugging or configuration challenge. Sifting through the minutiae of how a server or software functions is a great way to pass time. But this process doesn’t have to be an exercise in ineffective inefficiency. In fact, tools are available to you that go a very long way to make the editing of config files much, much easier. I’m going to introduce you to a few such tools, to ease some of the burden of your Linux admin duties. I’ll first discuss the command-line tools that are invaluable to the task of making configuration more efficient. Read more

Why Good Linux Sysadmins Use Markdown

The Markdown markup language is perfect for writing system administrator documentation: it is lightweight, versatile, and easy to learn, so you spend your time writing instead of fighting with formatting. The life of a Linux system administrator is complex and varied, and you know that documenting your work is a big time-saver. A documentation web server shared by you and your colleagues is a wonderful productivity tool. Most of us know simple HTML, and can whack up a web page as easily as writing plain text. But using Markdown is better. Read more