-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
should be "Same as macOS" and not "Same as MacOS" under brave colors selection #3832
Comments
I was going to grab this one as it seems like an easy one to fix 👍 @petemill mind if I take this one and give it a go if you haven't started/completed the work? |
Hi @aqeelparpia, this is a simple string change, but I'd be happy to help you contribute this change if you want to get used to the contribution process, if @kjozwiak doesn't have something in-progress. You should be able to search for "Same as MacOS" in a code editor to find the file. It's in a .grd file. |
@aqeelparpia all yours :) Appreciate the contribution! |
I'm having troubles setting up the project |
@aqeelparpia what steps have you done so far? Do you have XCode and the command line tools installed? You should be able to follow the steps here: |
Closing. Fixed with brave/brave-core#1909 |
@kjozwiak can you test this one since you have Mojave? |
@LaurenWags I tested this on from beta(0.65.x) to nightly (0.67.x) now and all are using correct string ( |
Verification PASSED on
@LaurenWags looks good 👍 |
Thanks @simonhong @kjozwiak for confirming 😄 |
Description
The
Brave colors
selection under Appearances should beSame as macOS
and notSame as MacOS
. Apple usesmacOS
.Steps to Reproduce
Brave colors:
underAppearances
Actual result:
Expected result:
Should be
Same as macOS
and NOTSame as MacOS
Reproduces how often:
100% reproducible using the above STR.
Brave version (brave://version info)
Reproducible on current release:
N/A as this hasn't made it into release.
Yes, reproducible under Nightly/Dev.
Website problems only:
Additional Information
The text was updated successfully, but these errors were encountered: