There are two reasons we changed over to using window.attachEvent. Firstly, its
is a IE only method so in effect it does its own branching for IE and secondly,
you can add multiple events on the same handler which means you could lump
several functions onto the onload handler rather than just the
awesome - thanks so much! Does that change have any negative side-effects?
On Mon, 28 Jun 2004 09:27:32 +0100, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> You can make the suckerfish dropdowns work on IE5 Mac by using window.onload to
> trigger the suckerfish function rather than window.atta
You can make the suckerfish dropdowns work on IE5 Mac by using window.onload to
trigger the suckerfish function rather than window.attachEvent
So you can use
if (document.all && document.getElementById) window.onload = sfHover;
instead of
if (window.attachEvent) window.attachEvent("onload", sfH
Kay,
Back in March, Kristen Morgan posted a link to the UDM website. The
canned solution they have come up with looks expensive, and it's not
lean and mean, but it seems to solve the compatibility issues pretty
much.
http://www.udm4.com/
-Hugh Todd
The original Suckerfish menus *do* work in IE5
MAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 28, 2004 12:46 PM
Subject: [WSG] IE5 Mac-friendly drop down menus
> Hi,
>
> We've got a client who uses Macs exclusively. Our fave dropdown menu
> of the moment, Son of Suckersfish, does not work in IE5 Mac.
&
Hi,
We've got a client who uses Macs exclusively. Our fave dropdown menu
of the moment, Son of Suckersfish, does not work in IE5 Mac.
The client is also maintaining the site using Contribute, and our
old-school brute force JavaScript dropdowns (CoolMenus) don't play
nicely with Contribute.
The o
