In theory, Javascript is great. But over the last year my company has actually started avoiding javascripted menus because of the problems that are inherent in client-based code. When a browser can't handle javascript, the results can be an unreachable site; the worse thing that happens when a CSS dropdown menu fails is that you simply don't get the dropdown part, but the main menu still displays fine. Or worst case scenario, someone see the lists expanded. Not pretty, but usable. Javascripted dropdown menus (often heavy in table structure), can cause unacceptable performance problems in CMS systems that pull navigation structure form a database. There's simply too much code on the page. Which is why we've stopped using javascript and gone to the sparse HTML markup styled with CSS. The performance gains have been tremendous. -- Carmen
On 10/6/05, Al Sparber <[EMAIL PROTECTED]> wrote: > > It's very nice, but still suffers from the same usability issues that > Suckerfish does - the menus are just too fast to snap shut. This > would, of course, be exacerbated if your examples had additional > nested lists. I still say that using the hover pseudoclass for popout > menus is not a good move. Javascript is the native behavioral medium > and provides the means to making a feature rich and more usable menu > that is styled using CSS, rather than operated with CSS. > > Al Sparber > PVII > http://www.projectseven.com > > "Designing with CSS is sometimes like barreling down a crumbling > mountain road at 90 miles per hour secure in the knowledge that > repairs are scheduled for next Tuesday". > > > ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
