Netscape 6 is buggy with capturing mouseout events

Looking for a workaround

[IanKelley]

I'm having a problem with a bug in the way Netscape handles mouseover/out. It will not always catch a mouseout event (as you've probably noticed).

The site in my profile is where I'm having problems... It works in Netscape 6+ but does bizarre things because of the mouseout bug.

I've left the JS and CSS in the main file so that it's easy to see what's going on.

Does anyone know how to get around this bug? With AOL considering making NS their default, there's no way I'm just going to turn functionality off for NS because of the bug.

Thanks much,

Ian

[Lisa]

What about having a function that resets things. Then you can trigger it with a mouseout still. Or other things could trigger it like a mouseover on another object or the document itself.

You could also set a timer that reset everything only if you are not currently hovering over that object.

[IanKelley]

Thanks... some of those things had crossed my mind.

The problem is I'm incredibly busy right now... I don't have time to write the script.

Because it's a universal problem with NS, I was hoping someone had a workaround script I could use.

[tedster]

You're already doing the one thing I know of to help Netscape catch mouseout events - the divs should have an ID, not just a class.

Ian, that's some mighty adventurous design there. When I get a chance, I'll dig into it a little deeper.

[IanKelley]

:-) Once I get the basics working it will use server side to show a different page for older/javascript disabled browsers.

Turns out it will also be showing a different page for the famed Opera. Wonderful as it may be, it has terrible DOM support.