While testing, I found that when a visit with a refresh presentation is proposed, TurboNavigatorHierarchyController will correctly pop (or dismiss) and then ask the session to reload. However, the session does not know that the topmost visitable changed, so a reload will end up reloading the last successfully loaded visit – the visitable that was just popped (or dismissed).
While testing, I found that when a visit with a refresh presentation is proposed,
TurboNavigatorHierarchyControllerwill correctly pop (or dismiss) and then ask the session to reload. However, the session does not know that the topmost visitable changed, so a reload will end up reloading the last successfully loaded visit – the visitable that was just popped (or dismissed).