fix(chromium): stop the app window opening on browser prompts - #177
Merged
Conversation
A first launch on Windows showed a Google account chooser before it showed lich: Chromium's profile picker, raised because the command line never named a profile and the machine's Chrome knew several accounts. Past it came the translate bar, offering to translate lich's own interface — the switch that was supposed to stop it, --disable-features=Translate, only asks at launch and in a vocabulary that moves between builds. Name the profile directory (Chromium suppresses the picker whenever the command line names one) and merge the two preferences that actually hold these down — signin.allowed and translate.enabled — into the profile before the browser opens. The merge runs on every launch so profiles created by an older lich are fixed too, keeps every other key Chromium wrote, preserves numbers exactly, and refuses to touch a Preferences file it cannot parse. A profile it cannot pre-configure is a warning, never a refused window. Windows and macOS remain unverified here — no hardware. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XqT84Egx81TK3TNzKL1G97
omartelo
added a commit
that referenced
this pull request
Aug 7, 2026
Move the [Unreleased] entries under a 0.27.0 heading and refresh the compare links. Also split an entry the previous release cycle merged into one. The Chromium prompts fix (#177) replaced the header line of the Windows icon fix (#175) instead of adding its own above it, leaving the icon entry's body attached to a fix it has nothing to do with. Both are separate Fixed entries again.
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.
A first launch on Windows showed a Google account chooser before it showed
lich: Chromium's profile picker, raised because the command line never named
a profile and the machine's Chrome knew several accounts. Past it came the
translate bar, offering to translate lich's own interface — the switch that
was supposed to stop it, --disable-features=Translate, only asks at launch
and in a vocabulary that moves between builds.
Name the profile directory (Chromium suppresses the picker whenever the
command line names one) and merge the two preferences that actually hold
these down — signin.allowed and translate.enabled — into the profile before
the browser opens. The merge runs on every launch so profiles created by an
older lich are fixed too, keeps every other key Chromium wrote, preserves
numbers exactly, and refuses to touch a Preferences file it cannot parse.
A profile it cannot pre-configure is a warning, never a refused window.
Windows and macOS remain unverified here — no hardware.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01XqT84Egx81TK3TNzKL1G97