-
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
Upgrade from Chromium 103 to Chromium 104. #23092
Comments
Verification PASSED on
History page has correct style_PASSEDTranslate bubble_PASSEDDisable - #brave-translate-go
Enable - #brave-translate-go
Hardware concurrency farbling works as expected_PASSEDDisucussed with @mkarolin, verified the issue #10808
[Note: the value should be between 2 and your actual processors count] Default/Block fingerprinting Aggressively block fingerprinting DeAmp and Speedreader work as expected_PASSEDDeAmp_PASSED(Refer the issue - #22228, discussed with @mkarolin )
Speedreader_PASSED
Settings UI and style works/looks correctly_PASSED
Settings comparison
Components updater
Brave startup calls
|
Verification
Devices: Performed checks for the Android affected areas mentioned in #23092 (comment) on nightly channel.
|
Labelling as |
Upgrade from Chromium 103 to Chromium 104.
https://chromium.googlesource.com/chromium/src/+log/103.0.5060.24..104.0.5112.29/?pretty=fuller&n=10000
QA tests:
This is a major Chromium version bump, please do full passes.
Desktop Affected areas:
Android Affected areas:
The text was updated successfully, but these errors were encountered: