Jan Rychter wrote:
> My main point is that there are very few cases where you swap in a > navigation widget in an AJAX request (without changing the URI), so I am > not sure if we want to build machinery to support that and run a tree > shakedown on every AJAX request. Perhaps it is enough to document it and > tell everyone to set :ajaxp nil when they are about to modify the > navigation hierarchy in the tree? That does sound like an acceptable solution. But I don't understand why we'd have to do a tree shakedown on every AJAX request because of this. Wouldn't it suffice to do so when a selector widget enters another widget's children list? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
