* fix(workspace): lead header Back to a parent route when the page opened the session
Settings, Discover, actor and in-portal search registered a header Back
that only ran Location.back(). As the first entry of the session (deep
link, reload, restored view) that did nothing in Electron and left the
app in a browser.
WorkspaceBackNavigationService.back(resolveParent) keeps Location.back()
while the previous entry is an in-app one, and while that is unknown
because the Navigation API is missing. Otherwise it opens the page's
parent with replaceUrl, so history Back cannot return to the page:
- Settings: the first workspace view (resolveDashboardPath()).
- Discover: the catalog section it lists (vod for movies, series for TV).
- Actor and search: the portal root, which redirects to its default
section within the same navigation.
The web E2E opens these pages in a fresh tab: a page.goto in the same
tab leaves the previous document behind, often at the parent's URL, so
history Back passed without the fix. Electron covers settings after a
window reload.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(workspace): lead first-entry Back to the parent without the Navigation API
Review follow-ups (Greptile):
- Without the Navigation API (older Safari and Firefox) back() always
called Location.back(), so a page that opened the session still left
the app. The service now tracks the router's in-app history depth there
(trackRouterHistoryDepth): first navigation 0, push +1, replacement
keeps it, a traversal restores the depth recorded for its entry. Depth
0 opens the parent; an unknown depth (an entry from before a reload)
keeps Location.back().
- Stalker's Discover (movie/tv section), actor and search pages now have
tests that they hand the service the parent under the portal :id.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(workspace): adopt the router navigation the Back depth tracker missed
Review follow-up (Codex, Greptile): the lazy workspace shell creates the
Back service after the first NavigationStart, so the tracker saw only its
NavigationEnd, left the depth unknown and counted the next push as the
first entry. It now adopts the router's current or last successful
navigation when it starts: a first navigation is depth 0, a later one
leaves the depth unknown (browser history Back), and a late start of the
adopted navigation is not counted again.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: 4gray <fourgray@proton.me>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
