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

Leftovers: OSS

  • Anonymous Open Source Projects
    He made it clear he is not advocating for this view, just a thought experiment. I had, well, a few thoughts on this. I tend to think of open source projects in three broad buckets. Firstly, we have the overall workflow in which the community works together to build things. This is your code review processes, issue management, translations workflow, event strategy, governance, and other pieces. Secondly, there are the individual contributions. This is how we assess what we want to build, what quality looks like, how we build modularity, and other elements. Thirdly, there is identity which covers the identity of the project and the individuals who contribute to it. Solomon taps into this third component.
  • Ostatic and Archphile Are Dead
    I’ve been meaning to write about the demise of Ostatic for a month or so now, but it’s not easy to put together an article when you have absolutely no facts. I first noticed the site was gone a month or so back, when an attempt to reach it turned up one of those “this site can’t be reached” error messages. With a little checking, I was able to verify that the site has indeed gone dark, with writers for the site evidently losing access to their content without notice. Other than that, I’ve been able to find out nothing. Even the site’s ownership is shrouded in mystery. The domain name is registered to OStatic Inc, but with absolutely no information about who’s behind the corporation, which has a listed address of 500 Beale Street in San Francisco. I made an attempt to reach someone using the telephone number included in the results of a “whois” search, but have never received a reply from the voicemail message I left. Back in the days when FOSS Force was first getting cranked up, Ostatic was something of a goto site for news and commentary on Linux and open source. This hasn’t been so true lately, although Susan Linton — the original publisher of Tux Machines — continued to post her informative and entertaining news roundup column on the site until early February — presumably until the end. I’ve reached out to Ms. Linton, hoping to find out more about the demise of Ostatic, but haven’t received a reply. Her column will certainly be missed.
  • This Week In Creative Commons History
    Since I'm here at the Creative Commons 2017 Global Summit this weekend, I want to take a break from our usual Techdirt history posts and highlight the new State Of The Commons report that has been released. These annual reports are a key part of the CC community — here at Techdirt, most of our readers already understand the importance of the free culture licensing options that CC provides to creators, but it's important to step back and look at just how much content is being created and shared thanks to this system. It also provides some good insight into exactly how people are using CC licenses, through both data and (moreso than in previous years) close-up case studies. In the coming week we'll be taking a deeper dive into some of the specifics of the report and this year's summit, but for now I want to highlight a few key points — and encourage you to check out the full report for yourself.
  • ASU’s open-source 'library of the stars' to be enhanced by NSF grant
  • ASU wins record 14 NSF career awards
    Arizona State University has earned 14 National Science Foundation early career faculty awards, ranking second among all university recipients for 2017 and setting an ASU record. The awards total $7 million in funding for the ASU researchers over five years.

R1Soft's Backup Backport, TrustZone CryptoCell in Linux

  • CloudLinux 6 Gets New Beta Kernel to Backport a Fix for R1Soft's Backup Solution
    After announcing earlier this week the availability of a new Beta kernel for CloudLinux 7 and CloudLinux 6 Hybrid users, CloudLinux's Mykola Naugolnyi is now informing us about the release of a Beta kernel for CloudLinux 6 users. The updated CloudLinux 6 Beta kernel is tagged as build 2.6.32-673.26.1.lve1.4.26 and it's here to replace kernel 2.6.32-673.26.1.lve1.4.25. It is available right now for download from CloudLinux's updates-testing repository and backports a fix (CKSIX-109) for R1Soft's backup solution from CloudLinux 7's kernel.
  • Linux 4.12 To Begin Supporting TrustZone CryptoCell
    The upcoming Linux 4.12 kernel cycle plans to introduce support for CryptoCell hardware within ARM's TrustZone.

Lakka 2.0 stable release!

After 6 months of community testing, we are proud to announce Lakka 2.0! This new version of Lakka is based on LibreELEC instead of OpenELEC. Almost every package has been updated! We are now using RetroArch 1.5.0, which includes so many changes that listing everything in a single blogpost is rather difficult. Read more Also: LibreELEC-Based Lakka 2.0 Officially Released with Raspberry Pi Zero W Support

Leftovers: Gaming