-
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 109 to Chromium 110 #27221
Comments
Verification
And
PASSED |
1.49.64 Chromium: 110.0.5481.52 | 1.47.186 Chromium: 109.0.5414.119 |
---|---|
brave://settings/clearBrowserData
brave://settings/appearance
Suggested sites
options is removed fromShow autocomplete suggestions in address bar
- Sidebar/Sidepanel options are located together
1.49.64 Chromium: 110.0.5481.52 | 1.47.186 Chromium: 109.0.5414.119 |
---|---|
brave://settings/web3
- Following options are moved from brave://settings/extensions
- Resolve Unstoppable Domains domain names
- Resolve Ethereum Name Service (ENS) domain names
1.49.64 Chromium: 110.0.5481.52 | 1.47.186 Chromium: 109.0.5414.119 |
---|---|
brave://settings/privacy
brave://settings/shields
Brave Wallet, both the page and panel interfaces - PASSED
PASSED
Cookie-related settings - PASSED
PASSED
- New setting
Block third-party cookies in Private
displayed in brave://settings/cookies
1.49.64 Chromium: 110.0.5481.52 | 1.47.186 Chromium: 109.0.5414.119 |
---|---|
Cookie settings:
- confirmed that cookie settings are retained in an upgraded profile
- confirmed cookies settings are working as expected in the brave://settings/cookies
- confirmed local and global cookies shield settings are working as expected
Verification as follows:
- opened cnn.com and confirmed default setting of
Block cross-site cookies
shown in the Shields panel - Opened
brave://settings/cookies
and confirmed default setting ofBlock third-party cookies
shown - opened
brave://settings/shileds
and confirmed default settings ofOnly cross-site
shown - changed the setting to
Block all cookies
inbrave://settings/cookies
- reloaded cnn.com and confirmed
Block all cookies
are shown in the Shields panel as expected - opened
brave://settings/shields and confirmed
Block cookies: All` shown as expected - Opened
brave://settings/cookies
and selectAllow all cookies
- reloaded cnn.com and confirmed that
Allow all cookies
setting shown in the Shields panel as expected - opened
brave://settings/shileds
and confirmed theDisabled
shown as expected - opened
brave://settings/cookies
and switch toBlock third-party cookies
- reloaded cnn.com and confirmed
Block cross-site cookies
setting - switched to
Allow all cookies
in the shields panel for cnn.com site - confirmed cnn.com is added to
Sites that can always use cookies
inbrave://settings/cookies
- confirmed brave://settings/cookies
is still shown
Block third-party cookies` setting - deleted www.cnn.com entry from
Sites that can always use cookies
inbrave://settings/cookies
- reloaded cnn.com and confirmed the setting was reverted to
Block cross-site cookies
in the shields panel - change to
Block all cookies
in the shields panel for cnn.com - returned to
brave://settings/cookies
and confirmed www.cnn.com entry is displayed inSites that can never use cookies
example | example | example | example | example |
---|---|---|---|---|
Brave Sync - PASSED
PASSED
- Covered the testing in Manual test run on Win x64 for 1.49.x - Nightly (Checking C110) #28066
- Additionally verified new
Delete Sync Account
functionality
Brave Search - PASSED
PASSED
- confirmed WDP infobar shown when Brave is a default search engine and
Web Discovery Project
toggle is enabled - confirmed links opened without issues on Search results page
- verified keyword search, URL-precedence and working as expected
- verified bookmark icon displayed in the omnibox autocomplete entry as expected
ex | ex | ex | ex | ex | ex |
---|---|---|---|---|---|
Side panel - PASSED
PASSED
- Confirmed that sidebar is shown left by default in the nightly channel
- Confirmed sidepanel opens when clicked on sidebar icon (i.e. Reading list and Bookmarks)
- Confirmed the side panel can be opened/closed when toolbar button is toggled on/off
- Confirmed reading list panel or bookmarks panel opened when clicked toolbar button (whichever was the last open)
- Confirmed when side panel opened, relevant sidebar icon (reading list or bookmarks) was selected
- Confirmed the toolbar button shown as selected with highlighted gray background
- Confirmed sidepanel can be opened/closed when bookmarks or reading list icons toggled on/off
- Confirmed that user can add the list of websites to the reading list by clicking on the +Add current tab in the panel
- Confirmed bookmarks are shown in the sidepanel
- Confirmed that sidepanel is shown in all the window types (Normal, PT, TOR)
- Confirmed if the sidebar is left aligned and the toolbutton is shown accordingly
- Confirmed if sidebar settings are changed to show on the right, sidepanel is shown on the right and toolbar is shown accordingly
- Confirmed vertical tabs working as expected after fix in 1.49.75
Example | Example | Example |
---|---|---|
Multiple profiles - PASSED
PASSED
- Confirmed that user can create the multiple profiles (e.g Profile 1 and Profile 2)
- open
brave://settings
and import bookmarks and add extensions inProfile 1
- Ensured that changes made in settings in
Profile 1
are NOT reflected inProfile 2
- Ensured that the
bookmarks
andextensions
are NOT reflected inProfile 2
- Ensured that updated rewards settings are specific to
Profile 1
and are not reflected inProfile 2
- Confirmed able to edit and delete profiles from Manage profiles
Brave startup calls - PASSED
PASSED
- Confirmed that only brave domains are listed in the Charles when the nightly build is launched with a clean profile
- Confirmed no calls to google, gstatic, etc domains when the nightly build is launched with a clean profile
Verified on
NTP Layout
Autoplay site setting
|
@MadhaviSeelam We usually ask @srirambv to run the web3 related affected areas as he is the web3 QA Spoc and he knows in and out of WEB3 and if we test this there are chances we may miss some testing around web3. Lets @srirambv test this and give a sign off @srirambv Could you please run |
We should be good with |
The above requires |
Upgrade from Chromium 109 to Chromium 110
https://chromium.googlesource.com/chromium/src/+log/109.0.5414.80..110.0.5481.40/?pretty=fuller&n=10000
QA tests:
This is a major Chromium version bump, please do full passes.
Desktop Affected areas:
iOS Affected areas:
Android Affected areas:
The text was updated successfully, but these errors were encountered: