Display Issue on Macintosh
Display Issue on Macintosh
We've used the newer version of the menu (5.0) on various sites with no problem thus far. However, we have one site: http://webdev.gslsolutions.com/jec.senate.gov/ in which the submenu will not show up on our only macintosh.
The machine is a Macintosh G4 running OS 10.3 Panther and two different browsers, Internet Explorer 5.2.3 and Safari 1.1. The far right submenu item for "Other Areas" will not show up on the IE browser for Macintosh.
The submenu works on IE 5+, Netscape 4.x, 6.0 and up on a PC and Safari 1.1 on the Mac, but the one IE for mac will just not display.
Does anyone have any ideas?
Thank you for your time!
David
The machine is a Macintosh G4 running OS 10.3 Panther and two different browsers, Internet Explorer 5.2.3 and Safari 1.1. The far right submenu item for "Other Areas" will not show up on the IE browser for Macintosh.
The submenu works on IE 5+, Netscape 4.x, 6.0 and up on a PC and Safari 1.1 on the Mac, but the one IE for mac will just not display.
Does anyone have any ideas?
Thank you for your time!
David
Well, the problem with doing it "your" way is that no one on here that I have seen is using this with Cold Fusion and Fusebox. Doing a search on Fusebox yields zero results. Fusebox and Cold Fusion code could not be entered on the menu_data page without calling it as a Fuseaction (and not an include.)
Trust me, I'd love to be able to use the menu as we did prior to version 5, but at this point, I haven't seen a way. Has anyone successfully used version 5 on a Fuseboxed Cold Fusion site?
Also, regardless of how I've included the code thus far, it still doesn't make sense that it works in every other browser, including an alternative Macintosh one, but not IE for mac.
For example, check out http://www.taskenvironmental.com. I used the version 5 menu there (with the same include method) and it works on all browsers we can test.
Thus my perplexion
Trust me, I'd love to be able to use the menu as we did prior to version 5, but at this point, I haven't seen a way. Has anyone successfully used version 5 on a Fuseboxed Cold Fusion site?
Also, regardless of how I've included the code thus far, it still doesn't make sense that it works in every other browser, including an alternative Macintosh one, but not IE for mac.
For example, check out http://www.taskenvironmental.com. I used the version 5 menu there (with the same include method) and it works on all browsers we can test.
Thus my perplexion
Oh, I have no doubts about that. This is the first mention of Fusebox I've seen.DaveBug wrote:Well, the problem with doing it "your" way is that no one on here that I have seen is using this with Cold Fusion and Fusebox.
Sure it does. IE/Mac never did really follow standards, and M$ was never that anxious to fix problems with it. Look at how fast they dropped the product when Safari was still in beta! I'm not knocking Mac (I used to work for Apple), but I sure am knocking IE.DaveBug wrote:Also, regardless of how I've included the code thus far, it still doesn't make sense that it works in every other browser, including an alternative Macintosh one, but not IE for mac.
Please post your problem in the Final Outstanding Bugs area to make sure Andy sees it. Maybe he'll have some ideas.
Thanks.
John
Well, I didn't do anything, but you're welcome. At least I'm a CF programmer!DaveBug wrote:Thanks for your help John, I'll get with Andy on it.
Just post it up top.
Argh, shame on you. Remember who can delete your postsDaveBug wrote:It wasn't that bad when I just had to code for IE and Netscape.. now we have a mac user in the office (blech)...
Now that I can relate to. I'm so tired of fighting NS4.x just because folks are too lazy to upgrade. Aw, don't get me started...DaveBug wrote:I've got to make sure it works on 4 stupid browsers now. Not fun...
John
To follow up in case anyone else has the problem. Andy suggested the fix was to move the main menu draw out of the table cell and up into the head tag. Doing so, and then calling the submenu in the table cell did the trick.
However, doing that now creates a one pixel line between each menu item on Macintosh Safari browsers.
So, the problem is fixed in IE, but creates another problem in Safari... argh!
However, doing that now creates a one pixel line between each menu item on Macintosh Safari browsers.
So, the problem is fixed in IE, but creates another problem in Safari... argh!
Thanks for the followup on the fix.
While Safari is 'final', IMHO it still has a lot of bugs. As usual, Andy has written around a lot of them, but there are still some remaining. I can't look at it here at work because I'm stuck on Windoze, but will try to remember to do it tonight from home.
I understand Safari was updated in Panther, but it sounds like some problems remain. It's tough trying to cover everything, given every browser has a different idea of what the 'standards' are, but you won't find anybody more dedicated than Milonic in getting things fixed.
While Safari is 'final', IMHO it still has a lot of bugs. As usual, Andy has written around a lot of them, but there are still some remaining. I can't look at it here at work because I'm stuck on Windoze, but will try to remember to do it tonight from home.
I understand Safari was updated in Panther, but it sounds like some problems remain. It's tough trying to cover everything, given every browser has a different idea of what the 'standards' are, but you won't find anybody more dedicated than Milonic in getting things fixed.
John
Yes John, it's been a bear trying to develop for Safari. I finally had to do a browser check and make lots of CFIF's for Safari exceptions.. saves a lot of headaches even though I hate doing it that way.
I have a related question. After the last Safari problem cropped up, Andy suggested I download RC 19. I did that, overwriting the old .js files and just left menu_data. Doing that, however, caused the menus not to work. Is there a step I'm missing?
Thanks for offering to take a look at it tonight on your Mac, our Mac guy is running Panther now and the latest version of Safari... 1.1.
Thanks for all the help thus far!
I have a related question. After the last Safari problem cropped up, Andy suggested I download RC 19. I did that, overwriting the old .js files and just left menu_data. Doing that, however, caused the menus not to work. Is there a step I'm missing?
Thanks for offering to take a look at it tonight on your Mac, our Mac guy is running Panther now and the latest version of Safari... 1.1.
Thanks for all the help thus far!
No, that should be it. Just replace all 3 of the menu code files. Your existing _data.js should be fine as is.DaveBug wrote:I have a related question. After the last Safari problem cropped up, Andy suggested I download RC 19. I did that, overwriting the old .js files and just left menu_data. Doing that, however, caused the menus not to work. Is there a step I'm missing?
No problem. Sent myself a reminder note home!DaveBug wrote:Thanks for offering to take a look at it tonight on your Mac, our Mac guy is running Panther now and the latest version of Safari... 1.1.
You're welcome. That's why we're here.DaveBug wrote:Thanks for all the help thus far!
John
OK, looking at the site in Safari1.0(v85), I see the main and sub-menu (I think there is only one - correct?). This is on a Dual G4 runing 10.2.8. There appear to be no problems. Did you make any changes?
I'm not sure about the 1px line between menus you mentioned earlier. I see the separators. Is that what you mean, or is there something else?
I'm not sure about the 1px line between menus you mentioned earlier. I see the separators. Is that what you mean, or is there something else?
John
Yes, the issue is only with IE, however, I fixed that by moving most of the calls up to the head tag.
As far as the spacers.. that is the problem I'm having now... and only on Safari. On menus where I have to use relative positioning, the menu items have a one space pixel between each item. Help? Is there some setting I'm not turning off?
If you want to see the settings for this menu.. actually, I'll post them here, so you can see if I'm leaving something out, or not settign spacer=0 somewhere.
As far as the spacers.. that is the problem I'm having now... and only on Safari. On menus where I have to use relative positioning, the menu items have a one space pixel between each item. Help? Is there some setting I'm not turning off?
If you want to see the settings for this menu.. actually, I'll post them here, so you can see if I'm leaving something out, or not settign spacer=0 somewhere.
Code: Select all
_menuCloseDelay=500 // The time delay for menus to remain visible on mouse out
_menuOpenDelay=100 // The time delay before menus open on mouse over
_followSpeed=5 // Follow scrolling speed
_followRate=50 // Follow scrolling Rate
_subOffsetTop=1 // Sub menu top offset
_subOffsetLeft=1 // Sub menu left offset
_scrollAmount=3 // Only needed for Netscape 4.x
_scrollDelay=20 // Only needed for Netcsape 4.x
with(menuStyle=new mm_style()){
onbgcolor="##4F8EB6";
oncolor="##ffffff";
offbgcolor="##DCE9F0";
offcolor="##515151";
bordercolor="";
borderstyle="solid";
borderwidth=0;
separatorcolor="##2D729D";
separatorsize="0";
padding=3;
fontsize="12";
fontstyle="normal";
fontfamily="Verdana, Tahoma, Arial";
pagecolor="black";
pagebgcolor="##82B6D7";
headercolor="##000000";
headerbgcolor="##ffffff";
subimage="";
subimagepadding="2";
overfilter="Fade(duration=0.2);Alpha(opacity=90);";
outfilter="randomdissolve(duration=0.3)";
}
with(SubMenuStyle=new mm_style()){
onbgcolor="##999999";
oncolor="##FFFFFF";
offbgcolor="##F1F2F2";
offcolor="##000000";
bordercolor="##999999";
borderstyle="solid";
borderwidth=1;
separatorcolor="##666666";
separatorsize="1";
padding=4;
fontsize="12";
fontstyle="bold";
fontfamily="Verdana, Tahoma, Arial";
pagecolor="black";
pagebgcolor="##82B6D7";
headercolor="##000000";
headerbgcolor="##ffffff";
subimage="";
subimagepadding="2";
overfilter="Fade(duration=0.2);Alpha(opacity=95);";
outfilter="";
}
with(milonic=new menuname("Main Menu")){
style=menuStyle;
top=75;
left=182;
alwaysvisible=1;
orientation="horizontal";
position="relative";
aI("image=#request.Path.Images#template/topmenu_budget.gif;overimage=#request.Path.Images#template/topmenu_budget_over.gif;url=#request.path.self#?FuseAction=Issues.Budget");
aI("image=#request.Path.Images#template/topmenu_economy.gif;overimage=#request.Path.Images#template/topmenu_economy_over.gif;url=#request.path.self#?FuseAction=Issues.Economy");
aI("image=#request.Path.Images#template/topmenu_health.gif;overimage=#request.Path.Images#template/topmenu_health_over.gif;url=#request.path.self#?FuseAction=Issues.Health");
aI("image=#request.Path.Images#template/topmenu_tax.gif;overimage=#request.Path.Images#template/topmenu_tax_over.gif;url=#request.path.self#?FuseAction=Issues.TaxPolicy");
aI("image=#request.Path.Images#template/topmenu_int.gif;overimage=#request.Path.Images#template/topmenu_int_over.gif;url=#request.path.self#?FuseAction=Issues.International");
aI("image=#request.Path.Images#template/topmenu_other.gif;overimage=#request.Path.Images#template/topmenu_other_over.gif;showmenu=OtherMenu");
}
with(milonic=new menuname("OtherMenu")){
style=SubMenuStyle;
<cfloop query="getIssues" startrow="1" endrow="#getIssues.RecordCount#">
aI("text=#getIssues.Issue#;url=#request.Path.Fusebox#Issues.Issue&Issue_ID=#getIssues.Issue_ID#;");
</cfloop>
}
drawMenus();
I just pulled your data file and am running it here under RC19 with no problems (removing the obvious CF stuff, of course - query and ## to #). I get the main menu boxes (no graphics) and the sub (looking for the query, but it does drop). This is IE6 because I'm stuck with Windoze during the day. But, it's working under RC19.DaveBug wrote:Also John, simply replacing the three files from RC 19 doesn't work for me.. it makes the menu not even appear Guess I'll have to start from scratch if I want to use the newer release.
The only other thing I did was to remove things you had defined but weren't using; e.g., subimage="";, so I also removed subimagepadding="2";. Also bordercolor="";, so I dumped borderstyle="solid"; and borderwidth=0;, etc. There were a few others as well. It may make no difference, but why carry them if not using?
Sent myself another reminder to look again tonight. However, it might be a day or two until I get back to you, as it looks like I'll be taking a rig and some supplies over to the fires in San Diego.
John