Comments on: Talking about JavaScript in London

By: Alice

Alice — Fri, 01 Dec 2006 13:28:05 +0000

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

By: Kabelmodem

Kabelmodem — Wed, 08 Nov 2006 20:47:52 +0000

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.

By: Webkatalog

Webkatalog — Wed, 25 Oct 2006 08:43:02 +0000

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

By: A2D Web Solutions

A2D Web Solutions — Mon, 25 Sep 2006 22:31:20 +0000

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.