Dreamweaver Nav. broken in Firefox PC

Question

I just discovered that the main navigation bar I put together
in Dreamweaver/Fireworks MX no longer works in Firefox on the PC
(even though it still looks fine in Explorer, and on all Mac
browsers). The site is
here (www.rgetter.com). The same
navigation exists on other pages. (I took the landing page off the
template to make troubleshooting easier.)
I'm on training wheels with JavaScript and not experienced
enough to debug the code. However, when I load the page in Firefox,
the JavaScript console does not list any errors. It's just that
none of the navigation shows up. I've tried backing off and using a
looser DOCTYPE after parsing the page a few times with the W3C's
tool, but still no luck.
I'd really like to know if this is something simple I'm
missing or do I need to rebuild the template from scratch with DW
8?
Thanks,
Ric

Answer 1

There are MUCH better ways than the FW8 method, too.
Check the uberlink and MacFly tutorials at PVII -
http://www.projectseven.com/
and the Navbar tutorial/articles at Thierry's place
http://tjkdesign.com/articles/dropdown/
Or this one (more recent article):
http://tjkdesign.com/articles/Pure_CSS_Dropdown_Menus.asp
Or to get it done fast, go here -
http://www.projectseven.com/tutorials/navigation/auto_hide/index.htm
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Ric G" <[email protected]> wrote in message
news:esj202$snr$[email protected]..
> Murray,
> Believe it or not, Andy Finnell's tale of unfortunate
events seems to have
> led
> me to a solution of sorts. I took the original graphic
from Fireworks MX
> and
> used Fireworks 8 to re-generate the code and it appears
to be much more
> Firefox
> 2.x friendly. I agree that this is butt-ugly code, but
until I can get
> better
> with CSS, it will have to do. I do know enough to
rewrite it to a point
> where I
> have "liquid" widths, at least. I should be able to
rebuild my template
> and
> re-apply it.
>
> Ric
>