Skip to content

Add configurable browser tab title (#1055) - #1077

Open
dillan wants to merge 2 commits into
mxtommy:masterfrom
dillan:feat/configurable-tab-title
Open

Add configurable browser tab title (#1055)#1077
dillan wants to merge 2 commits into
mxtommy:masterfrom
dillan:feat/configurable-tab-title

Conversation

@dillan

@dillan dillan commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Fixes #1055

Problem

The browser tab title is hardcoded to KIP, so users running several KIP instances (per boat / mast / engine) can't tell their tabs apart.

Fix

Adds a persisted browserTabTitle app setting (mirrors the existing instanceName pattern in SettingsService, defaulting to KIP), a Browser Tab field in Settings → Display, and an effect in AppComponent that keeps document.title in sync via Angular's Title service. A blank value falls back to KIP, and the resolver trims whitespace.

Tests

resolveBrowserTabTitle() is a small pure helper unit-tested for the default/trim behavior (committed test-first, RED then GREEN). The settings accessors mirror the established instanceName pattern, and the whole feature (types + AOT templates) is verified by a production build.

Notes

Existing stored configs without the field default to KIP on load, so behavior is unchanged for current users.

dillan added 2 commits June 23, 2026 16:55
Adds resolveBrowserTabTitle() plus its spec. The stub returns the raw value, so
the tests fail on purpose: a blank/whitespace value should fall back to "KIP" and
a set value should be trimmed.
resolveBrowserTabTitle() now trims the value and falls back to "KIP" when blank.

Adds a persisted browserTabTitle app setting (mirrors the instanceName pattern in
SettingsService, defaulting to "KIP"), a "Browser Tab" field in Settings > Display,
and an effect in AppComponent that keeps document.title in sync via Angular's Title
service. Lets users running several KIP instances tell their tabs apart.
@godind

godind commented Jul 1, 2026

Copy link
Copy Markdown
Collaborator

The idea is to use same tab and multiple dashboards rather than multiple tabs. Browsers handle background tabs processing much differently with CPU, network throttling or even full sleep.

Secondly KIP's primary designed goal is fullscreen, no browser UI and full touch so Tabs is not something I want to add focus on. Trying to keep code base focused.

Maybe some day...whom knows.

@dillan

dillan commented Jul 1, 2026

Copy link
Copy Markdown
Contributor Author

Sounds good. I appreciate the feedback.

@tkurki

tkurki commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

@godind pardon me, but imho you are needlessly limiting how Kip can be used. To me the feature seems useful and the changes seem small and local, adding a minuscule bit of complexity to the codebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Configurable browser tab title

3 participants