Show document paths in browser tab titles - #217
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
What changed
Added one route-aware title formatter and used it in both HubApp and VolumeApp. Project roots use the project name alone; file, folder, special-view, and past-version routes put the distinguishing route first. Configured branding remains the fallback when no project or volume context is available.
Updated the committed frontend bundle and added unit plus Playwright coverage for exact title formats and browser-history navigation.
Browser preview
Five real Chrome tabs against the seeded hub: project root, two documents, a nested document, and path-scoped History.
Verification
npm run buildnode --test src/router.test.ts— 24 passednpm run e2e -- browse.spec.ts --grep "tab title"— 1 passed./check-dist.sh—internal/webapp/static is freshKnown test gap
npm teststill has one pre-existing date-dependent failure insrc/lib/heat.test.ts:258: the fixture uses a fixed August 2026 date whilestaleNote()reads the real current time.