Repository navigation
Add Titanium Browser - #812
Merged
Merged
Conversation
offa
approved these changes
Nov 13, 2026
Owner
|
Given your insight and there's still no other comment in the linked ticket I guess it's ok here. Thanks for the PR and the details! 👍 |
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.
Adds Titanium Browser, a Chromium-based browser with extension support, built on GrapheneOS's Vanadium. Closes #790.
build.yml), with build provenance attestationsgoogle_api_keyand the client ID and secret to dummy valuesOn the codecs you mentioned:
args.gnsetsproprietary_codecs = trueandffmpeg_branding = "Chrome". In Chromium these flags build the patent-encumbered codecs (H.264, AAC) from FFmpeg's open source, rather than adding a closed binary. Cromite, already in the Browser section, sets the same two flags inbuild/cromite.gn_args. One more thing to weigh: the README recommends installing extensions from the Chrome Web Store, though local CRX and ZIP files work too.