ADC Rates Web Browsers For Javascript Compatibility
blamanj writes "The Apple Developer's site has an article about Javascript compatibility. They rate the 6 Mac browsers for feature-completeness in the Javascript arena. For those who don't read articles, Mozilla wins by a nose."
I'm not using a mac, but in mozillazine.org someone said the Mozilla team corrected the scrollbars bug in the latest builds.
In my pc seems to work, too.
I'm from Argentina: Tango, Asado, Mate, Gaucho, Maradona, YPF
I'll bet the reason Safari couldn't handle that XML -- which Mozilla 1.3b didn't run on my debian system until I copied it locally and fixed the XML problems -- was that it wasn't really XML. The MIME type is "text/plain" and it didn't have a proper XML declaration.
* And remember, it's spelled N-e-t-s-c-a-p-e, but it's pronounced "Mozilla."
Running IE6 on w2k, it fares quite well.
s ts/import.html
The only test it seems to have some issue with is the W3CDOM test where it creates form fields on the fly.
It creates the fields, but the radio buttons don't seem to accept a click. This may have to do with the fact that the radio buttons don't have a name attribute. I've noticed before that IE (at least mine) doesn't like unnamed radio buttons (as that's how it knows how to group them).
Otherwise, the other tests worked quite well.
--
Using Mozilla/Phoenix on win - the 'Import XML' test fails on my system.
From the Phoenix JS console:
Error: xmlDoc.getElementsByTagName("apple")[0] has no properties
Source File: http://developer.apple.com/internet/javascript/te
Line: 31
Wonder no more. IE6 on Win98 performed every test flawlessly. YMMV, IANAL, etc.
Overrated / Underrated : Moderation
This article isn't bad, but it only scratches the surface of a lot of more insidious problems with all the browsers "tested".
For instance, no real differentiation is made between DOM 0, DOM 1, and DOM 2 style events and their setters. There's not even a whisper about mutation events. The section on "display" properties totally misses the related (and more useful) problems of using attribute getters and setters in the various browsers. Ever tried setting a div to have overflow="scroll" on Safari?
One last nit: does anyone else find it uber-annoying that ADC's articles don't have authorship attribution?
Dojo: defanging browsers so you don't have to
Um, it's because Opera 6.x has no DOM support to speak of. V7 is showing real promise on the platforms it's available on, but the Opera 6 series is notoriously bad at anything that isn't straight-up HTML w/ CSS.
Dojo: defanging browsers so you don't have to
I don't have a Mac to test on but at least my old Nightly Build of Mozilla 1.3b (ID:2003021806) does render also the DHTML test perfectly[1]. You're right that the XML test is broken (the server is misconfigured).
[1] Or... it does display and remove the scrollbar as expected when the div goes over (under?) the right edge of viewport. However, it doesn't display the scrollbar when the div goes over the left border of the viewport, which I consider as a bug also. It's the bug ID:6976 in case you want to vote it. Don't post extra comments to that bug unless you have a fix.
_________________________
Spelling and grammar mistakes left as an exercise for the reader.
I just tested the sample scripts on Opera 7.0, Mozilla, and I.E. for Windows. I know this isn't a comprehensive list of Windows browsers, but it is what I have on hand.
Opera and Mozilla both handled everything flawlessly except for the XML. Neither seemed too happy with the imported XML text, instead remaining blank. On the other hand, I.E. rendered all of the above with no problems.
In any case, you shouldn't be importing your site's content as XML anyway, as another poster pointed out. If you have to, your site will be I.E. only for now. Unless they have a Mac.
This Sig is a mnemonic device designed to allow you to recognize this author in the future.