Subsequently, the first edition of the ECMA-262 specification was
accepted in 1997.
of ECMAScript. Other popular dialects are ActionScript and JScript (used
in Internet Explorer). A dialect can be said to be ECMA-262 compliant if
it satisfies the specification, and will often include proprietary
extensions that suit the context of the implementation.
As I mentioned last week, Microsoft introduced JScript as a reaction to
It sounds funny now, but some unloved proprietary features like the
blink tag were introduced during the browser wars. More
serious features were also introduced, but the usefulness of these
wasn't always apparent at the time.
A good example is XMLHttpRequest. Microsoft created the concept behind
it, although ActiveX was used. This shipped with Internet Explorer 5.0
in 1999. It wasn't until 2006 that the W3C published a working draft for
Another proprietary feature introduced by Microsoft was the
innerHTML property. Netscape added support for this
property in May 2000 due to its popularity and requests from the
With proprietary tags and properties like
not surprising that the development of the Document Object Model (DOM)
code is crippled without a clean API for manipulating elements, and
Microsoft and Netscape had a few false starts before standardisation.
Even modern browsers support it, despite its questionable usefulness.
Microsoft copied it for Internet Explorer 3.
If you started learning web development in the 90s, you'll probably be
familiar with the basic usage of DOM Level 0:
// Return all the forms on the page: document.forms // Return the first image: document.images // Changing a property: document.images.src = '/images/rollover.gif'
The World Wide Web Consortium (W3C) was founded in 1994, and had already
recommendation for DOM Level 1 was announced. Internet Explorer 5.0
shipped with partial support. It wasn't until 2000 that DOM Level 2 was
published and we finally had
getElementById and an event
In some ways this was already too late. Microsoft had its own event
model, which is still used today. If you've been following our Let's
Make A Framework series you should have seen example code for Microsoft
Meanwhile, as of version 4, Internet Explorer had been integrated into
Windows. This was the point at which Netscape's market share started to
suffer. Eventually it became clear that Microsoft's strategy was
potentially anti-competitive, and this prompted the antitrust case in
The case didn't help Netscape -- Internet Explorer 6 became the dominant
browser. This arguably ended an era of rapid innovation on the web, and
it wasn't until the excitement over Web 2.0 that IE started to seriously
Next week I'll continue this series, exploring the years leading up to
the Web 2.0 revolution.