The full context is that in the new design we remove the page navigation tabs when a page link with filters is taken. The goal was to avoid the confusion that arises when you have a filter link from Page 1 to Page 2, but the viewer user can still navigate to any page they want and even take additional links which is a state the breadcrumb can't really show and creates odd questions about what should happen if the same page is linked into twice.   UX was concerned that removing the page navigation tabs after clicking a simple link that didn't have filters was overly restrictive to common cases like an author building a table of contents on the first page. The simplest fix to avoid this was to omit these simple links from being part of the breadcrumb system altogether which also helps in cases where the flow of the report may be non-linear.   Sounds like the missing piece is that while it isn't necessary to lock a viewer into using the breadcrumb we should look at ways to still provide a navigational "go back" button that can function regardless of whether the breadcrumb is in use or whether the tabs are shown. Functionally I don't see any issues, so it mostly comes down to finding a stable position for it in the UI that doesn't conflict with the undo/redo buttons or the new edit/view toggle. I'll pass it along to the rest of the team and see where it goes. ... View more