Add browser domain overrides#77
Open
FuJacob wants to merge 1 commit into
Open
Conversation
75f66ee to
7308018
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.
Summary
Adds browser domain overrides on top of the existing app-level enable/disable rules so Tabby can behave differently per site inside Chrome-, Safari-, and other browser-based editors. The change threads focused-tab URL detection through the focus snapshot pipeline, persists explicit domain rules with registrable-domain default matching plus exact-host opt-in, and exposes those rules in the menu bar and Settings.
Validation
xcodebuild build -scheme tabby -destination 'platform=macOS'# ** BUILD SUCCEEDED **xcodebuild test -scheme tabby -destination 'platform=macOS'# Build completed, but the hosted macOS test bundle failed to load because of a local code-signing Team ID mismatch on tabbyTests.xctest.Linked issues
Fixes #26
Risk / rollout notes
Enablerules are persisted even when the parent browser app is disabled, so re-enabling the app later preserves the user’s per-domain intent instead of silently dropping it.