A lot of the stuff I'm finding in FF is under the hood and more for app developers. Let's see... * E4X (ECMA-357) * Native HTML Canvas support * Native SVG * Native XML DOM processing (not some multi-version ActiveX joke). Look at Mozilla Developer Central for more. Not to mention it's a better laid-out general reference area than what Microsoft provides for IE in MSDN. Then there's IE's (in)ability to pinpoint script errors when you have linked script files. It finds the proper line number, but thinks all code is in the main file, so you can't debug it. * Ability to print things that are legible more than 50% of the time... Oh, and type about:config in the address bar of FF for some other neat stuff. The only way I find to make a (reasonably) cross-browser app is to code in FF, then go back into IE and see what they implemented differently and fix it. If you go the other way you'll become trapping in IE's one-off "features".
---------------------- Chris Cole