On Sunday 18 December 2005 12:46 pm, Willie Wong wrote: > From my limited knowledge of javascript, I can't tell whether it is > a badly written javascript that parses in IE but not in Firefox, or > Firefox not supporting the full "standard", or perhaps the > site-designer used some IE-only extensions. >
As a web developer, allow me to interject a little bit of an explanation here. Not only is there a difference between Java and Javascript, there is a difference between Javascript and Jscript - the crap that IE invented. Then there's also ECMAScript - which was a standards body invented version of the other two. Add to that, there are multiple different Document Object Models between the different browsers, which is the language's object tree structure that defines how every element in the page and the code is named. So, since there are a half dozen or more different ways for the different browsers to try to execute the Javascript code, you'll find sites that will only support the browser that their programmer uses, or that will have half of the javascript on the page devoted to trying to figure out what browser you're using, followed by a bunch of if/thens with multiple different flavors of the code that will HOPEFULLY work for the browser that you're actually using, and sites that just disregard Javascript entirely rather than try to deal with the headaches. Search "javascript hell" on Google. Note the 3 million results. :-) Basically, if it isn't working right now, don't hold your breath for it to be fixed, either by the Firefox team, or the website developers. -- Eric Bliss systems design and integration, CreativeCow.Net -- [email protected] mailing list
