Vertical "son of Suckerfish" navigation - positioning question
I'm using a son of suckerfish menu - http://www.htmldog.com/articles/suckerfish/dropdowns/ . The one problem that I'm having with the menus is that if the vertical navigation gets too close to the viewable bottom of the page, the subnavigations continue off the bottom of the viewable page without having a good way to be able to get to it. Ideally, in this situation, it would be great if the subnavigational menu would be bottom justified, instead of top justified with the primary menu item, like:
menu item
menu item
menu item | submenu item
menu item | submenu item
menu item---| submenu item
--------------------------
instead of like:
menu item
menu item
menu item
menu item
menu item---| submenu item
--------------------------
| submenu item
| submenu item
Any easy solutions to this problem?
menu item
menu item
menu item | submenu item
menu item | submenu item
menu item---| submenu item
--------------------------
instead of like:
menu item
menu item
menu item
menu item
menu item---| submenu item
--------------------------
| submenu item
| submenu item
Any easy solutions to this problem?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You understand what I've done. Thanks for the clarification on what your looking for..
ASKER
Anyone else?
Or, alternatively, is it possible to overcome the fact that you can't use the mouse wheel in netscape to scroll through the page?
Or, alternatively, is it possible to overcome the fact that you can't use the mouse wheel in netscape to scroll through the page?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your comments. We have actually done some work so that the main categories are clickable, and lead to a static list of subcategories, as well as having static links on the site as well - I think we're well covered for the accessibility issues at this point. We're just trying to make the menus work a little better than they probably can :)
The one problem I have with javascript menus (and I know a couple of pretty good scripts) is that they end up getting to be very 'heavy' in size fairly quickly. As we are already producing a database-driven web site, we're hoping to have light-weight menus.
The one problem I have with javascript menus (and I know a couple of pretty good scripts) is that they end up getting to be very 'heavy' in size fairly quickly. As we are already producing a database-driven web site, we're hoping to have light-weight menus.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Believe me, I do understand... it wouldn't be my first choice to use these menus - but I'm not the site owner :)
ASKER
Thanks all - I'm sorry to have left this one standing! When the client realized that they could use the scrollbar on their mouse, and that only about 0.5% of their users were using Netscape, they calmed down and decided to use as is.
We also added a way for them to go to a full index of the items, too.
We also added a way for them to go to a full index of the items, too.
ASKER
However, this is a little bit different - I'm trying to deal with a scrolling page. I have a page which is more than one screen-ful deep. My problem isn't that the physical page cuts off the subnavigation items, but that the subnavigation items are partly beyond the scroll. The ideal solution would be for the menu in this case to be bottom justified instead of top justified.