Upgrade from Chromium 111.0.5563.50 to Chromium 111.0.5563.64.

[mkarolin]

Minor Chromium bump

https://chromium.googlesource.com/chromium/src/+log/111.0.5563.50..111.0.5563.64?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]

The above requires 1.49.120 or higher for 1.49.x verification 👍

[LaurenWags]

Quick update re: the work that remains on each platform/OS in terms of checking/verifying C111:

Still requires a check re: affected C111 areas

• macOS x64 - Affected areas mentioned via Upgrade from Chromium 110 to Chromium 111 #28288 (comment) have been partially verified under Upgrade from Chromium 111.0.5563.41 to Chromium 111.0.5563.50 #28839 (comment). Remaining checks from Upgrade from Chromium 110 to Chromium 111 #28288 (comment) are:
  • Cookie/Content settings
  • Verify that Brave policies (such s TorDisabled) work correctly when set
  • Brave Sync
  • PDF extension
• Linux - Affected areas mentioned via Upgrade from Chromium 110 to Chromium 111 #28288 (comment) need to be checked/verified
• Android Tablet - Affected areas mentioned via Upgrade from Chromium 110 to Chromium 111 #28288 (comment) need to be checked/verified

Affected C111 areas completed and require a quick spot check of 111.0.5563.41

• Win x64 - Just needs a simple spot check re: 111.0.5563.64 on 1.49.x as the affected areas where checked via Upgrade from Chromium 110 to Chromium 111 #28288 (comment) & Upgrade from Chromium 110 to Chromium 111 #28288 (comment).
• Android ARM - Just needs a simple spot check re: 111.0.5563.64 on 1.49.x as the affected areas where checked via Upgrade from Chromium 110 to Chromium 111 #28288 (comment).

[btlechowski]

Verification passed on

Brave	1.49.120 Chromium: 111.0.5563.64 (Official Build) (64-bit)
Revision	c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}
OS	Ubuntu 18.04 LTS

Full verification done it #28839 (comment)

[Uni-verse]

Verified on Samsung GS 21 5G using version:

Brave	1.49.120 Chromium: 111.0.5563.64 (Official Build) (64-bit) 
Revision	c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}
OS	Android 13; Build/TP1A.220624.014

• Version bump
• Check branding

Example	Example

[Uni-verse]

Verified on Samsung Galaxy Tab S7 running Android 12 using version:

Brave	1.49.120 Chromium: 111.0.5563.64 (Official Build) (64-bit) 
Revision	c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}
OS	Android 12; Build/SP2A.220305.013

Spot checked affected areas mentioned in #28288 (comment) and checked versioning/branding items.

Ads notifications	Web notifications	NTP	NTP (bg images off)	share menu	Uphold	Version

[MadhaviSeelam]

Verification PASSED using

Brave | 1.49.120 Chromium: 111.0.5563.64 (Official Build) (64-bit)
-- | --
Revision | c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}
OS | Windows 11 Version 22H2 (Build 22621.1265)

[stephendonner]

Carried on from #28839 (comment), which is now QA/No

Verification PASSED using

Brave	1.49.120 Chromium: 111.0.5563.64 (Official Build) (x86_64)
Revision	c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}
OS	macOS Version 13.3 (b) (Build 22E7752300g)

Content settings - PASSED

• Confirmed that Shields settings is been added in brave://settings/content (more info: Add Brave's Shields setting to brave://settings/content #12782)
• Added few sites to shields up and shields down list and ensured sites got added to shield settings list
• Open the sites (which are added in shield down list) in PT/TOR tab windows and ensured shields are down as expected
• Confirmed content settings are working as expected
• Confirmed cookies settings are working as expected

1. Block cookies content settings - PASSED

• Open a site cnn.com
• Open content settings for cnn.com
• Block content settings for Location and Window management
• Reload cnn.com
• Ensured that Location and Window management permission are blocked for cnn.com
• Open brave://settings/cookies and Block all cookies
• Reload cnn.com and ensured that all cookies are blocked on cnn.com

Example	Example	Example	Example	Example	Example

2. Block scripts content settings - PASSED

• Block the JavaScript for a site via brave://settings/content/javascript
• Open the site ensured JavaScript blocked for the site
• Open a bunch of websites and ensured JavaScript is not blocked

Example	Example	Example	Example

3. Block autoplay global settings - PASSED

• Block the youtube.com autoplay content global settings via brave://settings/content/autoplay
• Open youtube.com and ensured no videos are autoplayed
• Click on a video and play the video manully, wait till the 1st video ends
• Ensured 2nd video is not autoplayed

Example	Example	Example	Example

Verify that Brave policies (such as TorDisabled) work correctly when set - PASSED

1. installed 1.49.120
2. launched Brave
3. pasted defaults write com.brave.Browser TorDisabled -bool true into a Terminal/console window, and pressed return
4. launched Brave
5. confirmed that the New Private Window with Tor menu option is removed
6. opened brave://policies
7. confirmed the correct entry for TorDisabled set to true is reflected
8. shut down Brave
9. pasted defaults delete com.brave.Browser TorDisabled
10. launched Brave
11. confirmed New Private Window with Tor menu option returned

Example	Example	Example	Example	Example