Facing the acid test
DEEP in the bowels of a Las Vegas hotel, a smiley face and the
words “Hello World” display on a web page. Applause breaks out. The
page is called the Acid2 Browser Test, and the web browser is a
preview of Internet Explorer 8, presented by its platform
architect, Chris Wilson.
“Thank you from the bottom of my heart,” says a member of the
audience to more applause from about 3000 web designers and
developers at the Mix08 conference, where Microsoft showed its
latest internet technology.
The Acid2 page (webstandards.org/action/acid2/) was created by
the Web Standards Project to test whether a browser conforms to the
official standards for describing page layout, mainly focusing on
cascading style sheets (CSS).
The reason for the applause is twofold: first, until now
Microsoft’s web browser, used by an estimated 75 per cent of
net surfers (although Firefox has been eroding that hold), has
never been close to passing the test; second, Internet Explorer’s
poor standards compliance causes significant extra work for web
designers.
When users navigate to a web page, they expect it to look and
work the same whatever the browser or operating system they are
using. Achieving this is difficult. Different browsers display the
same page differently, with IE often the worst offender.
Web developers now hope they do not have to insert conditional
code to account for these differences, but can deliver a standard
page to all browsers. “CSS support in IE8 looks thus far to be
very, very promising,” says Eric Meyer, an independent expert in
the field. “It’s very important, because the level of CSS support
in IE7 and IE6 has served as a brake on advanced CSS adoption by
authors, limiting them to less-advanced techniques and
capabilities.”
Internet Explorer has a curious history. Six versions were
released between 1995 and 2001, the time of the “browser wars” with
Netscape. Microsoft won the war and then did not release another
major version of the browser for five years - long enough for it to
become thoroughly outdated.
IE’s CSS implementation fell far behind that of other popular
browsers. In late 2006 Microsoft released IE7, which fixed some
problems but still lagged behind its rivals. “Differences between
browsers simply waste too much developer time,” says Dean
Hachamovitch, Microsoft’s general manager for IE, without
mentioning the extent to which Microsoft created the problem.
Mr Hachamovitch, who has led the Explorer team since 2003,
explains why Microsoft took so long to address these deficiencies.
“It comes down to what we were doing with our time,” he says.
“Between 2001 and 2003 we were building what you experience now as
Windows Presentation Foundation and Silverlight.”
These technologies display not HTML, the language of web pages,
but XAML, Microsoft’s proprietary code for creating rich visual
content.
“In 2003 and 2004 we were making IE secure,” he says, referring
to the security-focused Windows XP Service Pack 2.
Security remained the theme in IE7. The dilemma was that fixing
bugs introduced compatibility problems. “You can’t just flick a
switch and have all the browsers in the world change, or have all
the servers and services in the world change,” Mr Hachamovitch
says. The result was that some websites looked worse than before,
because they detected that IE was accessing them and delivering
content that took into account presumed peculiarities.
Microsoft’s answer was to build “compatibility modes” into IE8.
The manner in which this was done remains controversial. The
question was whether to default to the IE7 compatible mode, or
default to the better standards mode, Mr Hachamovitch says. “(We
found in) releasing IE7 that web developers were slow to modify
their sites. We wanted to keep the web working.”
Microsoft initially announced that IE8 would behave by default
like IE7. Page designers would have to include special code to turn
on IE8’s standards support. The decision was greeted with a hail of
protest because it might perpetuate a non-standard web.
Earlier this month, Mr Hachamovitch announced that Microsoft had
changed its mind. “We’ve decided that IE8 will, by default,
interpret web content in the most standards compliant way it
can.”
Apparently the key to that change of heart was a separate
strategic announcement last month, covering what Microsoft calls
interoperability principles and promising “open connections to its
products, support for industry standards and data portability”.
According to Mr Hachamovitch, Microsoft now had “a more
interoperable way; a more compatible way”.
It sounded good, but what about browser scripting. The context
is important. Mr Hachamovitch had already stated that Microsoft
spent three years neglecting IE for the sake of a more proprietary
technology, which is now appearing on the web as a browser plug-in
called Silverlight.
This is similar in some ways to Adobe’s Flash, and supports rich
multimedia effects within web pages as well as the ability to run
applications written in Microsoft’s .NET Framework.
Silverlight and Flash applications in effect bypass the browser.
Web standards advocates are wary of them because they replace the
open web with content that depends on a proprietary plug-in.
The Mozilla Foundation, creator of the cross-platform Firefox
browser, prefers to upgrade the capabilities of the browser itself.
A key component of this is JavaScript, the programming language
that runs in the browser and that is standardised by ECMA, the
European standards body, under the name ECMAScript. Mozilla is keen
to see the current JavaScript upgraded to a far more powerful
version called ECMAScript 4.0.
“Why do we care about ECMAScript 4.0?” asks Mozilla’s
vice-president of engineering, Mike Schroepfer. The answer is that
JavaScript is the language of the net. We want to keep pushing that
technology forward to make it easier for people to build bigger,
faster, more secure websites.”
Asked if Microsoft will implement ECMAScript 4.0, Mr
Hachamovitch prevaricates and talks about competing demands on the
IE development team.
“Right now there isn’t really an ECMAScript 4 offering to
implement, there is an ECMAscript for discussion.” he says.
The Guardian
