Back To Start Of Archive
Taken From The Forum: Help & Support for DHTML Menu Version 5+
Forum Topic: Click to view post
Last Updated: Saturday July 14 2012 - 06:07:42
Collapsible Menu problems
Poster: chinaski2
Dated: Thursday February 1 2007 - 1:59:58 GMT
Ok I have been banging my head against a wall for a while over this. I have pretty extensive experience with the Milonic menu and this one has me stumped.
http://209.19.69.211/sacto/sun_overview.html
This is the 3rd level of the site. You can see the issues on any but this one makes it the easiest.
I have a horizontal all image menu that works ok except that when you first load the page the sub menus are not aligned correctly. This happens in IE7, FF, and Safari. I have checked both Mac and PC. Once you mouse over them the first time they will reset themselves to the proper spots.
The left nav is the collapse menu. It has several problems. The first is it is not staying relatively positioned. If you load the page it works ok until you either have to scroll down or if you make the page wider or more narrow. Then the sub elements move with the page. Only the main nav is relative.
Also the sub items appear to have extra borders sometimes. If you look at the last item you can see it clearly in all browsers. I have check this on pretty much all the browsers I hae available and it happens on all.
Any help is greatly appreciated.
Poster: chinaski2
Dated: Thursday February 1 2007 - 19:44:08 GMT
I have been testing this further and it appears to be a problem with the collapse menu itself as I have a pretty base install now here:
http://209.19.69.211/collapse2/
I am using treemenu 1.27 and milonic 5.770
The behavior is still pretty much the same.
I think I might be on to something with the position="" settings. They seem to vary for the child elements if I play with them. I have used "relative", "absolute", and "inherit". They all have different effects. None are the desired though.
ANYONE??
Poster: chinaski2
Dated: Tuesday February 6 2007 - 18:05:39 GMT
I can't believe no one has any suggestions. I guess I will have to look for another solution.
Poster: Ruth
Dated: Wednesday February 7 2007 - 5:45:31 GMT
Hi,
Sorry, I should have posted that it seems to be something in the offsets and I've reported it to Milonic. I'm sure Milonic will have a fix as soon a possible, they are pretty good a getting on things quickly.
I did find a workaround that seems to work so you might want to try it out and see if it works for you, but it has been reported so hopefully it will be fixed soon.
Put all the submenus back into the collapse_data.js file. Leave the main menu in the table with the drawMenus() at the end and also put a drawMenus() at the end of the collapse_data.js file. Then at the top of that file, after the subOffsetLeft=0; add buildAfterLoad=true;
That seems to work.
Ruth
Poster: chinaski2
Dated: Wednesday February 7 2007 - 20:40:34 GMT
I think I have tried this option a few times.
The problem is that when you expand a branch and then resize the window none of the items move with the rest of the menu. Please see example with your suggestions here:
http://209.19.69.211/collapse2/
The news menu is as close as I can get and it is rather cludgey.
Poster: Ruth
Dated: Thursday February 8 2007 - 2:58:41 GMT
Hi,
I've posted this new information to Milonic. As soon as they find the problem, it will be fixed.
Ruth
Poster: Ruth
Dated: Friday February 9 2007 - 5:13:46 GMT
Hi,
I'm sorry to be the bearer of bad tidings but....
The bad news is, I have no idea when this will be fixed. It is being worked on. Unfortunately, I didn't realize this menu has not been placed in final release so many people have used the collapse version without problems, that I hadn't noted it is still under development. It has not been moved to final release becauses of various issues, this being one of them and since it's still under development it may take until the tree/collapse program is finished to fix this issue.
What might be good news, if you can use the menu absolutely positioned, it seems it will work OK as long as it is positioned using the top=; and left=; At least it worked in my tests.
Sorry, for the bad news. Can you give me an idea of your layout, there might be another solution.
Ruth