The spry pop-up menu I built in Adobe Dreamweaver worked fine in my old Firefox, I updated Firefox today and the menu no longer works--despite disabling the pop-up blocker in Firefox preferences...what's the problem??? I need the menu to work!!!

Question

I built a new pop-up menu for my website using Spry in Adobe Dreamweaver. Because of some differences in .HTML and .XHTML
it took me days to get it right. I tested every variation in Firefox until it worked perfectly. Today, I installed the newest version of Firefox and now the pop-up no longer works. I changed the preferences in Firefox to disable to pop-up blocker and it STILL DOESN'T WORK...although an older style of pop-up menu (menu machine) which is no longer supported by Adobe, DOES WORK.
HELP!!! THIS IS IMPORTANT.

Answer 1

pixlor:
OP is using CS3 and the menu blog is talking about the menus
in earlier
versions of FW, so *most* of the points made in the blog
don't apply.
That's not to say that using CS3 pop-up menus is a *good*
thing....
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"pixlor" <[email protected]> wrote in
message
news:gbce7b$a50$[email protected]..
>
quote:
Originally posted by:
captainbianco
> I agree completely and totally, and I will haha but I'd
like to get this
> one
> fixed if I can. You can view the page here
>
http://www.flooringanswers.com/nysurfaces/index2.htm
> Hover over the letters to see the pop-up menu's. The one
over "t" is the
> problem.
> Under Flooring, for example, you have a div with id of
> MMMenu0910163730_1_1
> (ugh). Under that are four items and they have their own
IDs:
> MMMenu0910163730_1_1_Item_0
> MMMenu0910163730_1_1_Item_1
> MMMenu0910163730_1_1_Item_2
> MMMenu0910163730_1_1_Item_3
> MMMenu0910163730_1_1_Item_4
>
> Your CSS file, however, doesn't have location
information for the ..Item_4
> object.
>
> That's just from a quick, cursory look. In order to fix
this, you're going
> to
> have to go through it line by line and debug it. By the
time you do this,
> you
> might be better off getting something else and starting
from scratch.
>
> Read this:
>
http://www.losingfight.com/blog/2006/08/11/the-sordid-tale-of-mm_menufw_menujs/
>