[thelist] Browser Stats

[.jeff]

rick,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Rick [Kitty5]
>
> > Global Browser Usage Share as of 8/26/02:
> > Microsoft    95.97%
> > Netscape 3.39%
> > Other .64%
>
> Looks like a good enough reason to stop supporting
> ns4.x to me!
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

yeah, to me too.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> - however once you do, you will quickly discover IE6 is
> not the wonder browser you once thought (Mozzy Rocks!)
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

ha, as if.  when developing anything even remotely complicated with scripting and/or full-on dhtml i find the experience *much* more painful and generally more likely to be fruitless with moz than i do with ie6.  i can write most anything for ie6 without having to look it up.  when i do have to look it up the documentation is easy to find, has lots of understandable information, and working examples.  when i try to build it to work for moz (even from scratch) i find myself constantly searching for documentation.  what i've been able to find uses extremely terse language, has very few examples, and is generally incomplete.

i'll agree that moz has alot of really cool features, but it's not the wonder browser so many people think it is.

<tip type="DHTML" author=".jeff">

If you're tracking mouse events and are referencing the tagName of the object moused over, beware of disabled text.  It doesn't have a tagName and will therefore cause your script to throw an error when you try to access the tagName of the object being moused over.  solution?  just check the typeof object.tagName to see if it's undefined before trying to access it.

obj = window.event.srcElement;
if(typeof obj.tagName != 'undefined')
{
  // ......
}

</tip>

thanks,

.jeff

http://evolt.org/
jeff at members.evolt.org
http://members.evolt.org/jeff/