> I'll pitch in quickly -- I think these two are orthogonal. Hidden panes > are, well, hidden, they are not rendered. Use them for supplementing > your navigation with things which are accessible via URIs on the same > level, but not visible in the navigation menu (think /admin interface, > /terms-of-service or similar).
Yes, that's what I think, too. > Disabled panes are rendered in the menu, but can't be clicked. I am not > sure what the semantics are for when the user accesses a disabled pane > via an URI. I think they were just disabled while the menu itself was being rendered. > I'm sorry I can't be of more help, but I'm rather busy with other stuff > right now :-( That's alright. I've fixed some bugs already, refactored a bunch of stuff and have the failing tests down below ten. Should be ready for merging soon. Thanks for the design and coding! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
