Member Avatar for stevenpowen

When I use the Fly-out Jscript menu at the following address I can't view
the menu on a Apple MAC using IE 5, Safari 2, or Foxfire. Can anyone please take a look at the site I have designed and tell me if I'm leaving out browser specific code that would enable MAC machines (and browsers made for the MAC) to understand the code and display the menu. The menu works on PC browsers IE and Netscape. How do I implement the correct DOM for the other browsers.

My site:
and
Site where the Fly-out menu was pulled from:

Thanks for any help

flyoutmenus.zip (32 KB)
  • 2 Contributors
  • 2 Replies
  • 131 Views
  • 13 Hours Discussion Span
  • Latest Post Latest Post by stevenpowen

Dani AI

Generated

A few focused checks will usually surface why a PC-tested fly-out fails on Mac browsers. posted that the menu hides on Mac browsers and rightly suggested contacting the script author, but the fastest wins are a quick DOM/CSS audit and feature-based fixes: confirm a proper DOCTYPE so the page runs in standards mode (Quirks vs Standards), open the browser error console to catch exceptions, and search the script for Windows-only DOM usage such as document.all or window.event.

Common actionable steps:

  • Open the Mac browser console (or Safari/Firefox dev tools) and reload to find the first JS error; fix that and the menu often appears.
  • Replace browser sniffing with feature detection and use standard DOM methods like document.getElementById. Attach events with a fallback, for example:
if (el.addEventListener) {
  el.addEventListener('mouseover', openMenu, false);
} else if (el.attachEvent) {
  el.attachEvent('onmouseover', openMenu);
}
  • Check CSS/positioning: clipped fly-outs are usually caused by an ancestor with overflow:hidden, incorrect z-index, or unexpected position creating a new stacking context. As a test, move the menu node to document.body at runtime so it is not constrained by parent containers.

Validate the page markup with the W3C validator and use progressive enhancement: get a small working example in all target browsers, then integrate it. If supporting very old Mac browsers (IE5 Mac, Safari 2) is required, test on actual Mac builds or a cross-browser service; otherwise consider a lightweight, widely tested menu approach and focus on feature detection patterns described on MDN (Feature detection).

Recommended Answers

All 2 Replies

Member Avatar for tgreer

That's a complex script... your best bet for support for pre-made scripts is to contact the script author. While I will not discourage anyone who wants a challenge to jump in help you out, I have to say it would be quite a commitment to ask.

Member Avatar for stevenpowen

Thanks: the microsoft site isn't very specific about authors and I didn't get any response from the Newsgroups there either. Maybe I'll try again. I was hoping for a easy fix - as always - it's never easy.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.