Description Susan McCourt 2011-05-04 13:21:51 EDT

the code that remembers navigator expansions is traversing the expanded nodes in the order they were expanded.  This ensures that we open the parent before we open, say, an expanded child.

The problem, though, is that the expand is asynchronous, so we need to be smarter about expanding the items in the cache.  If the item is nested under the previous item, it needs to be expanded only after the first expansion is complete.

I hadn't noticed this because I tend to link directly into the tree and expand only a couple levels.  but if you are using a deep tree it's immediately apparent.