> Ok, I understand what you meant now. however, isn't the navigation > widget supposed to submit requests via ajax by default? The links are > rendered by RENDER-LINK with ajaxp set to T [(render-navigation-menu) - >> (render-menu) -> (render-link)].
> It doesn't seem to be doing so: > httpfox shows normal GET requests without the additional headers that > would indicate an ajax request, and the effects aren't executed. So > what am I missing about the navigation widget? You're missing the ETYPECASE clause in RENDER-MENU. The :AJAXP T clause only fires when the passed menu item is a function. This is a convenience branch for rendering actions in a menu. The normal branch entered is the one for strings which renders plain non-AJAX URIs with (:a :href ...) The reason behind making nav links non-AJAX is to ensure a basic level of bookmarkability that AJAX doesn't give you (except by hijacking fragment identifiers). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
