That solution is not ideal in my case. My ListView uses a virtualized data source and I have to make another async service call for each item that in the list so depending on when the user clicks an item there could be some complicated timing issues occurring
if I just store the datasource off. I think my best solution is to load an Iframe above my listview that takes up the entire screen and show the details in there. I then can simply hide the iframe when the user wants to navigate back to the ListView.
This maintains my current scroll position and keep my items from be reloaded. This is still not as easy as it sounds since I need to handle the events the navigator object handles and I am not sure how tombstoning will effect this page. I have noticed
a lot of the third party apps (Dailymotion, USA Today, etc.) in the marketplace do not handle this problem at all. This renders that app almost useless. It is a shame this is not handle automatically by the framework like it is on the windows phone.