Working together for standards The Web Standards Project

JavaScript was just one of the items on the menu at this year’s @media conference in London. The panel on JavaScript libraries featured Simon Willison, Stuart Langridge, Peter-Paul Koch, Dan Webb and the host with the most, Cameron Adams. It was a highly entertaining romp through the pros and cons of using other people’s code. Simon has posted his notes from the panel. An audio recording will be available in the future; subscribe to the @media podcast if you want to hear it.

The DOM Scripting Task Force was well represented during the conference as well as afterwards. At the @media social, Ian Forrester posed some questions to PPK, Christian Heilmann, Dean Edwards and myself. It was (partially) recorded on video, along with the CSS Chat Show and the Accessibility Game Show. The videos are available for your downloading pleasure.

There’ll be more London-based JavaScript goodness at the Web Standards Group London Meetup when Christian delivers a presentation on Maintainable JavaScript.

Your Replies

#1 On September 25th, 2006 5:31 pm A2D Web Solutions replied:

I think it was Simon posted his (very good by the way), many of sites & applications probably only require a few core things – dom manipulation, proper event binding, a little AJAX and a maybe couple of spiffy show/hide effects for polish.

#2 On October 25th, 2006 3:43 am Webkatalog replied:

To me the comments from Chris Wilson on implications of IE7 for web designers are very interesting. I just implemented an AJAX-driven application (meta search for hotel and flight bookings) using layers etc. and the difference from IE6 to IE7 was *big*. IE7 does better in CSS standars now, but unfortunately it is as incompatible to FF and Opera as IE6. I don’t think it’s Microsoft’s fault, but for web designers it is now even worse – we have to support IE6, IE7, FF15, FF20, Opera8, Opera9….

regards, Marc

#3 On November 8th, 2006 3:47 pm Kabelmodem replied:

You won’t find the problems in JavaScript.
The Problem is the implementation of DOM in the Browser, not JavaScript itself.
Here is a simple example:
To access an element in the DOM, the programmer would type , ” document.getElementById(“elementID”) “. This is an improvement over most web browsers implementations of DOM element access. Internet Explorer, before coming into DOM compliance, necessitated that the developer access the DOM via an array of all elements as such , “document.all.[elementName] “. Whereas this was handy, it did not comply with the DOM syntax aforementioned. The Gecko Engine, seen in Firefox and all of it’s derivatives, has been W3C compliant for quite a while.

#4 On December 1st, 2006 8:28 am Alice replied:

I missed this great confrence in London due to family matters but was wondering when the next @media confrence was in London or Europe?

Return to top

Post a Reply

Comments are closed.

All of the entries posted in WaSP Buzz express the opinions of their individual authors. They do not necessarily reflect the plans or positions of the Web Standards Project as a group.

This site is valid XHTML 1.0 Strict, CSS | Get Buzz via RSS or Atom | Colophon | Legal