If you use a compose element (who's activate function returns a promise) within a ViewModel, the router complete event seems to fire before the promise is resolved which causes a jumpiness in the navigation. If we remove the compose element from the view model everything works fine.
Is this behavior intended? Shouldn't the router wait for the entire view to compose include any composed elements ( before considering navigation complete?
The process looks like this:
Navigate from page A to Page B
Router.IsNavigating = true
Router.IsNavigating = false (at this point page A still shows as Page B hasn't fully been composed)
If you use a compose element (who's activate function returns a promise) within a ViewModel, the router complete event seems to fire before the promise is resolved which causes a jumpiness in the navigation. If we remove the compose element from the view model everything works fine.
Is this behavior intended? Shouldn't the router wait for the entire view to compose include any composed elements (
The process looks like this: