Register Cate as a macOS browser and handle external web links - #694
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
2 participants
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.
Cate did not register HTTP and HTTPS in its macOS Info.plist, so macOS could not offer it as a default browser. This change registers both schemes and opens external links in visible browser panels, including during startup and session restoration. Browser panels work without a project folder; other panel types retain their folder requirement.
The existing
com.cate.appbundle ID, signing identity, and product name are preserved so this can ship through the normal update path. Apple Developer registration for that existing ID must be resolved before enabling the restricted browser passkey entitlement. This PR does not enable passkeys yet.Validation: 40 focused tests, production build, targeted ESLint, and all platform CI checks passed for the URL-handling implementation. The signed packaged app was tested with startup and later web links loading real pages. Full typecheck still has two pre-existing WebGL/GPUCanvasContext errors in
territoryGL.test.tsx. The rebuilt arm64 app retains com.cate.app and HTTP/HTTPS registration, passes deep/strict code-signature verification, and satisfies the exact designated requirement extracted from the installed v2.0.2 app. This verifies signature compatibility, not a complete Squirrel update transaction. The local validation build is not notarized or published.The initial v2.0.3-beta.1 release was withdrawn because it changed the bundle ID and would require users to reinstall. Do not publish that artifact or the existing beta tag. A replacement release needs a new version and a verified update path.
Apple Developer Support case 102971033975 requests resolution of the existing com.cate.app registration conflict and correction of entitlement request 5P6HK94RQN, which referenced the withdrawn build and alternative identifier. Apple approval and native passkey integration remain outstanding.