Skip to content

Use tor colors for connect buttons

Merge Info

Related Issues

Backporting

Timeline

  • Immediate: patchset needed as soon as possible
  • Next Minor Stable Release: patchset that needs to be verified in nightly before backport
  • Eventually: patchset that needs to be verified in alpha before backport
  • No Backport (preferred): patchset for the next major stable

(Optional) Justification

  • Emergency security update: patchset fixes CVEs, 0-days, etc
  • Censorship event: patchset enables censorship circumvention
  • Critical bug-fix: patchset fixes a bug in core-functionality
  • Consistency: patchset which would make development easier if it were in both the alpha and release branches; developer tools, build system changes, etc
  • Sponsor required: patchset required for sponsor
  • Localization: typos and other localization changes that should be also in the release branch
  • Other: please explain

Merging

  • Merge to tor-browser - !fixups to tor-browser-specific commits, new features, security backports
  • Merge to base-browser - !fixups to base-browser-specific commits, new features to be shared with mullvad-browser, and security backports
    • NOTE: if your changeset includes patches to both base-browser and tor-browser please clearly label in the change description which commits should be cherry-picked to base-browser after merging

Issue Tracking

Review

Request Reviewer

  • Request review from an applications developer depending on modified system:
    • NOTE: if the MR modifies multiple areas, please /cc all the relevant reviewers (since gitlab only allows 1 reviewer)
    • accessibility : henry
    • android : clairehurst, dan
    • build system : boklm
    • extensions : ma1
    • firefox internals (XUL/JS/XPCOM) : jwilde, ma1
    • fonts : pierov
    • frontend (implementation) : henry
    • frontend (review) : donuts, richard
    • localization : henry, pierov
    • macOS : clairehurst, dan
    • nightly builds : boklm
    • rebases/release-prep : dan, ma1, pierov, richard
    • security : jwilde, ma1
    • signing : boklm, richard
    • updater : pierov
    • windows : jwilde, richard
    • misc/other : pierov, richard

Change Description

/cc @donuts

We add the tor-button class to the bridge dialog connect buttons, and the "Choose a bridge for me" button.

We also make all tor-button's share the same focus outline. I was unsure about this because changing from one focus outline colour to another can be a little jarring. But ultimately I was swayed by:

  1. The tor purple and focus outline blue are too similar. So having a blue button with a purple outline, or vis-versa did not look good.
  2. Destructive buttons in firefox use a red outline that matches the button background color.

Note, as a result, only the .tor-button elements in "about:tor" have the purple outline. Everything else uses default blue.

How Tested

Checked each dialog, before and after we are bootstrapped. If we are not bootstrapped the "connect" button should not be shown, and the primary button should be blue instead.

Also checked "about:torconnect" and the "connect" urlbar button.

Edited by morgan

Merge request reports

Loading