Upgrade from Chromium 121.0.6167.57 to Chromium 121.0.6167.75.

[mkarolin]

Minor Chromium bump

https://chromium.googlesource.com/chromium/src/+log/121.0.6167.57..121.0.6167.75?pretty=fuller&n=10000

QA tests:

• Check branding items
• Check for version bump

Additional checks:

• No specific code changes in Brave (only line number changes in patches)

[kjozwiak]

Adding QA/Blocked as the above will be uplifted into 1.62.x via brave/brave-core#21593. We'll run through the above once it lands in 1.62.x.

[kjozwiak]

The above requires 1.62.148 or higher for 1.62.x verification 👍

[kjozwiak]

Quick overview of the work remaining re: affected areas due to C121 on the following platforms:

Platforms that only require a spot check due to already completing full check of the affected areas mentioned via #34702 (comment):

• Windows - Requires quick spot check, full check completed via Upgrade from Chromium 120 to Chromium 121. #34702 (comment).

• Android ARM - Requires quick spot check, full check completed via Upgrade from Chromium 120 to Chromium 121. #34702 (comment).

• Android Tablet - Requires quick spot check, full check completed via Upgrade from Chromium 120 to Chromium 121. #34702 (comment).

Platforms that still need to check/verify the affected areas due to C119 changes as per #34702 (comment):

• macOS - Still requires a pass through the affected areas
• Linux - Still requires a pass through the affected areas

[GeetaSarvadnya]

Verification PASSED on

Brave | 1.62.149 Chromium: 121.0.6167.75 (Official Build) (64-bit)
-- | --
Revision | ff84587bd70af9fcbcbe59fc5194ca65082759c4
OS | Windows 10 Version 22H2 (Build 19045.3930)

[LaurenWags]

Verified cases below, to be continued with #35493 (comment).

Brave | 1.62.149 Chromium: 121.0.6167.75 (Official Build) (x86_64)
-- | --
Revision | ff84587bd70af9fcbcbe59fc5194ca65082759c4
OS | macOS Version 13.6.3 (Build 22G436)

Encountered #35495 while testing (not specific to Chromium 121).

Verifying desktop affected areas from #34702 (comment):

Tab strip looks correct (vertical and horizontal) - PASSED

Horizontal Tabs

• Confirm that the tab strip looks good in a Card hover mode
• Confirm that the tab strip looks good in a Card mode`
• Confirm that the tab strip looks good in a Tooltip mode

Card hover mode

Card with Preview hover mode

Tooltip hover mode

Vertical Tabs

• Confirm that the tab strip looks good in a Card hover mode
• Confirm that the tab strip looks good in a Card mode`
• Confirm that the tab strip looks good in a Tooltip mode

Card hover mode

Card with Preview hover mode

Tooltip hover mode

Check that channel name is displayed correctly in brave://version (Nightly, Beta, Release) - PASSED

• Confirmed that channel name looks correct in nightly, beta, and release builds via brave://version/
• Confirmed that channel name looks correct in nightly, beta, and release builds via brave://settings/help

Example	Example

Tor Use Bridges setting works - PASSED

1. Clean profile 1.62.x RC
2. Open brave://settings/privacy
3. Make sure Select a built-in bridge is selected and obfs4 is populated in the dropdown
4. Click on Apply changes
5. Ensured that the following domains opened in a Tor window without issues:
   • brave.com
   • duckduckgo.com
   • https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/
   • check.torproject.org (ensured that hard refreshing gets a new circuit/IP)

Use bridges	Example	Example	Example	Example	Example

6. Confirmed the following sites opened via "Open in Tor" button and navigated to .onion URL:
   • brave.com --> https://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/
   • nytimes.com --> https://www.nytimesn7cgmftshazwhfgzm37qxb44r64ytbb2dj3x62d2lljsciiyd.onion/

Example	Example

Example	Example

7. Close the TOR window and disable Use Bridges settings and click on Apply Changes

Example	Example

8. Repeat the steps 5 and 6 and ensure that the TOR network is connected successfully

Example	Example	Example	Example	Example

Example	Example

Example	Example

HTTP -> HTTPS upgrade works - PASSED

Case 1 - PASSED

• Confirmed that visiting http://https-everywhere.badssl.com automatically upgrades from HTTP --> HTTPS
• Confirmed that visiting http://https-everywhere.badssl.com doesn't upgrade to HTTPS when shields are disabled
• Confirmed that http://https-everywhere.badssl.com auto-upgraded to HTTPS once the shields is re-enabled
• Confirmed that http://https-everywhere.badssl.com doesn't upgrade to HTTPS when Connections upgrade to HTTPS was disabled
• Confirmed that http://https-everywhere.badssl.com auto-upgraded to HTTPS once Connections upgrade to HTTPS has been enabled

Example	Example	Example	Example

Case 2 - PASSED

Default - Upgrade connections to HTTPS, Standard - PASSED

1. installed 1.62.x RC build
2. launched Brave
3. confirmed Upgrade connections to HTTPS is set to Standard in brave://settings/shields
4. loaded http://insecure.arthuredelstein.net
5. loaded http://http.badssl.com
6. loaded http://upgradable.arthuredelstein.net
7. opened a New Private Window with Tor and loaded each of the above

default	insecure.arthuredelstein.net	http.badssl.com	upgradable.arthuredelstein.net

Tor

insecure.arthuredelstein.net	http.badssl.com	upgradable.arthuredelstein.net

Upgrade connections to HTTPS, Strict - PASSED

1. installed 1.62.x RC build
2. launched Brave
3. changed Upgrade connections to HTTPS to Strict in brave://settings/shields
4. loaded http://insecure.arthuredelstein.net
5. loaded http://http.badssl.com
6. loaded http://upgradable.arthuredelstein.net
7. opened a New Private Window with Tor and loaded each of the above

Upgrade connections, Strict	insecure.arthuredelstein.net	http.badssl.com	upgradable.arthuredelstein.net

Tor

insecure.arthuredelstein.net	http.badssl.com	upgradable.arthuredelstein.net

Upgrade connections to HTTPS, Disabled - PASSED

1. installed 1.62.x RC build
2. launched Brave
3. changed Upgrade connections to HTTPS to Disabled in brave://settings/shields
4. loaded http://insecure.arthuredelstein.net
5. loaded http://http.badssl.com
6. loaded http://upgradable.arthuredelstein.net
7. opened a New Private Window with Tor and loaded each of the above

Upgrade connections, Disabled	insecure.arthuredelstein.net	http.badssl.com	upgradable.arthuredelstein.net

Tor

insecure.arthuredelstein.net	http.badssl.com	upgradable.arthuredelstein.net

Rewards, Bookmarks, VPN, Wallet buttons in the toolbar look correctly - PASSED

Default settings/enabled

• Confirm that the Rewards, Bookmarks, VPN and Wallet settings are enabled by default via brave://settings/appearance
• Confirmed that the Rewards, Bookmarks, VPN and Wallet buttons are shown correctly in the toolbar
• Confirmed that click on each button works as expected

Example	Example

When the settings are disabled

• Disable Rewards, Bookmarks, VPN and Wallet settings via brave://settings/appearance
• Confirmed that the Rewards, Bookmarks, VPN and Wallet buttons are not visible in the toolbar

Example	Example

Tor works with a proxy set - PASSED

Tor works with Proxy

Case 1:

1. Launch Brave with --args --enable-logging=stderr --proxy-server="socks5://localhost:9000"
2. Visit brave.com
   ---> site doesn't load as expected due to the proxy directing traffic to localhost
3. Visit https://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/
   ---> site loads since Tor doesn't use the proxy

Example	Example

Case 2:

1. Confirm Charles Proxy is set up and launched
2. Start Brave with Charles enabled
3. Go to brave.com in a normal window and confirm that the request is able to be seen in Charles
4. Open a Tor window
5. Navigate to https://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/
6. Confirm the site loads as expected and is not shown in Charles

Example	Example

Tor works without Proxy

1. Clean profile 1.62.x RC
2. Ensured that the following domains opened in a Tor window without issues:
   • brave.com
   • duckduckgo.com
   • https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/
   • check.torproject.org (ensured that hard refreshing gets a new circuit/IP)

Example	Example	Example	Example	Example

3. Confirmed the following sites opened via "Open in Tor" button and navigated to .onion URL:
   • brave.com --> https://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/
   • nytimes.com --> https://www.nytimesn7cgmftshazwhfgzm37qxb44r64ytbb2dj3x62d2lljsciiyd.onion/

Example	Example

Example	Example

[hffvld]

Verified on Pixel 7 using version(s):

Device/OS: Pixel 7 / panther_beta-user 14 AP11.231215.007 release-keys
Brave build: 1.62.149
Chromium: 121.0.6167.75 (Official Build) (64-bit) 

---

1	2

[kjozwiak]

Labelling the above as release-notes/exclude & QA/No in favour of #35493 (comment). @LaurenWags see #35493 (comment). Can remove the in-progress label whenever you're ready 👍

[hffvld]

Verified on Galaxy Tab S8 using version(s):

Device/OS: Galaxy Tab S8 / gts8wifixx-user 13 TP1A.220624.014 release-keys
Brave build: 1.62.149
Chromium: 121.0.6167.75 (Official Build) (64-bit) 

---

1	2