Repository navigation
Install: default the extension IDs so a bare tailtab install works - #4
Merged
Merged
Conversation
…ailtab install` works on a Firefox-only machine
Stocist
force-pushed
the
fix/default-extension-ids
branch
from
September 10, 2026 03:17
fde0d15 to
5ba3c87
Compare
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.
A Windows user on Reddit ran
tailtab.exe installby hand and got:Both IDs were required, but they are fixed values: the Chromium one is derived from the key in
manifest.chromium.jsonand is the same in every Chromium browser, and the Gecko one is the add-on's ID. They are now defaults, sotailtab installalone registers the released extension. The flags stay for custom builds.install.DefaultEdgeID/install.DefaultGeckoID, with a test that both pass the validators.