matt andrews wrote: > On 30/03/06, Thierry Koblentz <[EMAIL PROTECTED]> wrote: >> matt andrews wrote: >>> In which case I'd hide all but the currently-visible element with >>> CSS. Presumably you're using progressive enhancement, so the "tab" >>> links (to show non-currently-visible elements) will do full page >>> loads if Javascript is not enabled, so you can reveal the >>> appropriate element with CSS on the subsequent page load (and hide >>> the previous one). >> >> That's much more work though. Does it worth it? The only advantage I >> can see is that in JS challenged UAs, only the related sub-menu >> would be opened vs. the whole enchilada. > > That, and also that you don't get weird visual effects during load > *with* a Javascript-enabled UA.
But using JS to plug the sheet, as suggested earlier, takes care of that issue. Much less work, good result. Regards, Thierry | www.TJKDesign.com ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
