When the user has an offline page on the nav stack, but is online, if we navigate the stack backwards (back button), and try to replace the offline version of the page with an online version, it is instead putting the new navigation at the forward end of the stack, which puts the navigation into an infinite loop as the user presses back (the user sees the same pages again and again as they press back, never going back to the rest of the pages.) 

To "fix" this, we turned off the Offline->Online reloading feature if the navigation stack is navigating backwards (actually, any time the nav position is not at the very front of the stack).  However, this isn't the best fix, it would be better to fix the problem so that we can re-enable the feature.

This may mean modifications to how the should_replace_current_entry field works in relation to the back stack.