>>When drodown or flyout menus have more than 6 or 7 items, it is probably >>time to rethink the navigation design.<<
>>This seems less of a CSS issue and much more of a design/IA issue.<< Although, normally, I'd agree with both of you, for the question I posed these comments don't follow through :( Bascially, I'm a subcontractor for the designer. And I know you all have had those clients that will *just not listen* to you when you say something can't be done. This is the issue we're having. The client wants the Son of Suckerfish dropdowns (which were implemented and work great). But we can't touch the database, and the idea of "more" added to the bottom was brought up and all that - they don't want it. They just want the menu to be on the site, and have the lists populated by the database with no further effort from them. They will not subcategorize, and they will not add a "more" thing to the bottom. All attempts at trying to talk them into this have failed. They simply will not take "no" for an answer, and they don't want to pay for me to redo the whole thing over again, they want me to "fix" what I've already done - so I'm just trying the last few resources I have before I tell them what they want simply isn't possible for the last time :) I *do* know that if you click a menu item and then push the "down" button on your keyboard, the menu stays open while the page scrolls on down and you can see the rest (at least in Firefox)- but I doubt the general public knows this! So, it still leaves the question as to whether or not you can accomplish the dropdown effect, but have something in place that causes the menu to "wrap" when it hits the bottom of the viewable area - or if it's possible to have an "Expandable" dropdown on click (not hover) with no javascript. All of my searches have come up with a big fat "no" on the issue...but I was hoping with the great minds here that you might have a suggestion or two (other than rethinking the navigation - BELIEVE me, that's been tried!) with the CSS that might satisfy everyone. For the moment, I've put in an expandable, CSS-based menu that requires Javascript to make the "onclick" work. It looks fine, and - although I haven't sent it in yet - I think they'll be happy with it. My concern is the javascript - what happens if someone comes and their browser has javascript turned off? I do know with SOS menus, they list will be displayed as a list - which is utterly acceptable. But I don't know how this will react in the same situation (which really isn't your all's problem ;) ) But anyway, if anyone *does* have a CSS-based solution to the "menu going past the viewable area of the screen" issue, it'd be greatly appreciated :) Thanks! ~Shelly ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
