brave / brave-browser

Brave browser for Android, iOS, Linux, macOS, Windows.
https://brave.com
Mozilla Public License 2.0
17.85k stars 2.34k forks source link

Remove v1 shields UI (a.k.a. shields extension panel) #23285

Closed petemill closed 2 years ago

petemill commented 2 years ago

Now that Shields v2 UI (a.k.a. WebUI Bubble Panel) has been released for some time, we can remove the older version.

This will reduce resource usage as there are some background event hooks constantly running as part of the previous version of the UI.

Test Plan

GeetaSarvadnya commented 2 years ago

Verification PASSED on


Brave | 1.42.68 Chromium: 103.0.5060.114 (Official Build) beta (64-bit)
-- | --
Revision | a1c2360c5b02a6d4d6ab33796ad8a268a6128226-refs/branch-heads/5060@{#1124}
OS | Windows 10 Version 21H2 (Build 19044.1826)

Testplan

Case 1 : Verify Shield v2 UI and controls - PASSED - Confirmed that `shield v1` is not present even behind the `brave://flags` - Confirmed shield v1 code is removed from 1.42.x - Confirmed that clicking on shield on any site opens up `shield v2` - Confirmed that `controls on the shield v2` are shown correctly when the shield is UP - Confirmed that clicking on the controls `Filter lists` redirected to the custom filter page - Confirmed that clicking on the `Global defaults` in the shield redirects to the global shield settings page - Confirmed that clicking on the ads and trackers count opens up the panel with blocked scripts/content - Confirmed that `controls on the shield v2` are shown correctly when the shield is DOWN - Confirmed that trackers count is NOT shown on the shield v2 when the shield is DOWN - Confirmed that clicking on the `Learn more` and `Report site` are redirected to the intended pages when the shield is DOWN Example | Example | Example | Example | Example | Example -- | -- | -- | -- | -- | -- ![image](https://user-images.githubusercontent.com/38657976/179692069-34e088c3-6ac7-4ee3-b3d3-a7a598d8a79d.png) | ![image](https://user-images.githubusercontent.com/38657976/179692158-8b37b25f-52d0-4e6a-8d12-7432fd91df57.png) | ![image](https://user-images.githubusercontent.com/38657976/179692281-2e4c5b82-217f-401d-a347-7b1bcc0f9455.png) | ![image](https://user-images.githubusercontent.com/38657976/179694219-9e40cc7d-2ee6-46c8-9558-d9d4d01ec034.png) | ![image](https://user-images.githubusercontent.com/38657976/179694378-b5860f66-ef9e-4b04-9d6d-6f7021a96641.png) | ![image](https://user-images.githubusercontent.com/38657976/179694895-f64c3ced-1ad7-49c4-b374-84e1bac4a801.png)
Case 2 : Verify Cosmetic filtering-PASSED Case 1: Clean profile - Ensured custom filter is working as expected - Open any site and click on any object/element on the UI and select the `Block element` context menu and ensure that the element gets blocked on the UI - Remove custom filters and reload the page restores the blocked content on the UI/page. Currently, a browser restart is required to restore the blocked content which is known, encountered #21797 - Select `Manage custom filters` on PT/TOR window is causing the brave crash, encountered https://github.com/brave/brave-browser/issues/24086#issuecomment-1189367310 - Confirmed that element/object can be blocked on the Guest window, but removing custom filter doesn't restore the blocked element on the page, required browser restart but the user will lose the browser session and it's of no use restoring the blocked content, added comments in https://github.com/brave/brave-browser/issues/21797#issuecomment-1189948905 Case 2: Upgrade profile - Install `1.41.88` beta build, open a few websites and block the contents on the webpages and ensured elements are blocked - Go to brave://settings/help and auto upgrade the profile to `1.42.65` - Open brave://settings/shields/filters and ensured blocked elements are still present in the custom filters section - Open webpages and ensured elements/objects are still blocked on the UI - Remove the blocked content from brave://settings/shields/filters - Restart the browser and ensued blocked elements are restored on the webpages **_1.41.88_** | **_1.42.65_** -- | -- ![image](https://user-images.githubusercontent.com/38657976/179931602-a8f8df10-19d4-44c7-9dc3-68c9db4ce542.png) | ![image](https://user-images.githubusercontent.com/38657976/179931847-e68edc43-5ccf-4d0e-9a61-1ce9ec08c51e.png)
Case 3 : WDP-PASSED - Verified WDP scenarios and ensured WDP works fine
**`Test Case #1`** - `SE other than Brave` * launched `1.31.85 Chromium: 95.0.4638.50` * changed the SE default to `Bing` via `brave://settings/search` * visited `brave://prefs-internals` and ensured that `"brave_search_visit_count": 0` * opened https://search.brave.com via new tabs 10 times * refreshed a single tab that has https://search.brave.com opened ~15 times * ensured that `"brave_search_visit_count": 0` under `brave://prefs-internals` **`Test Case #2`** - `Brave as default SE (opening new tabs)` * launched `1.31.85 Chromium: 95.0.4638.50` * ensured that `Brave` is the SE via `brave://settings/search` * opened `https://search.brave.com` in `3` new tabs and ensured that the `WDP` modal appeared without any isssues (3) * dismissed the modal using the `No Thanks` button * ensured that `"brave_search_visit_count": 3` via `brave://prefs-internals` * opened `https://search.brave.com` in `7` new tabs and ensured that the `WDP` modal appeared without any isssues (10) * ensured that clicking on `Learn More` opens https://brave.com/privacy/browser/#web-discovery-project in a new tab * ensured that `"brave_search_visit_count": 10` via `brave://prefs-internals` * dismissed the modal using the `No Thanks` button * opened `https://search.brave.com` in `10` new tabs and ensured that the `WDP` modal appeared without any isssues (20) * dismissed the modal using the `X` button * ensured that `"brave_search_visit_count": 20` via `brave://prefs-internals` * opened another ~30 tabs with https://search.brave.com and ensured the modal isn't being displayed again **`Test Case #3`** - `Brave as default SE (Refreshing Tab)` * launched `1.31.85 Chromium: 95.0.4638.50` * ensured that `Brave` is the SE via `brave://settings/search` * opened `https://search.brave.com` in a single tab * refreshed the same tab `2` times and ensured that the `WDP` modal appeared without any issues (3) * dismissed the modal using the `No Thanks` button * refreshed the same tab `7` times and ensured that the `WDP` modal appeared without any issues (10) * dismissed the modal using the `X` button * refreshed the same tab `10` times and ensured that the `WDP` modal appeared without any issues (20) **`Test Case #4`** - `Brave as default SE (Duplicating Tabs)` * launched `1.31.85 Chromium: 95.0.4638.50` * ensured that `Brave` is the SE via `brave://settings/search` * opened `https://search.brave.com` in a single tab * duplicated the tab `2` times and ensured that the `WDP` modal appeared without any issues (3) * dismissed the modal using the `X` button * duplicated the tab `7` times and ensured that the `WDP` modal appeared without any issues (10) * dismissed the modal using the `No Thanks` button * duplicated the tab `10` times and ensured that the `WDP` modal appeared without any issues (20) **`Test Case #5`** - `Enabling WDP` * launched `1.31.85 Chromium: 95.0.4638.50` * ensured that `Brave` is the SE via `brave://settings/search` * went through the above cases and ensured that clicking on `Turn on` correctly enabled `WDP` via `brave://settings/search` on `3`, `10` & `20` * ensured that once `WDP` is enabled, the modal isn't being displayed again (example, accept on `3` and open `10` & `20` and ensure the modal isn't being displayed) * ensured that `"brave_search_visit_count"` stays at `3` if `WDP` was enabled on the first modal * ensured that `"brave_search_visit_count"` stays at `10` if `WDP` was enabled on the second modal * ensured that `"brave_search_visit_count"` stays at `20` if `WDP` was enabled on the third modal **`Test Case #6`** - `No Thanks` * launched `1.31.85 Chromium: 95.0.4638.50` * ensured that `Brave` is the SE via `brave://settings/search` * went through the above cases and ensured that selecting `Don't ask again` stops displaying the modal on `10` & `20` * ensured that dismissing the modal via `X` & `No Thanks` works correctly when `Don't ask again` has been selected * ensured that `"brave_search_visit_count"` stays at `3` if `Don't ask again` was selected and the modal dismissed * ensured that `"brave_search_visit_count"` stays at `10` if `Don't ask again` was selected and the modal dismissed

Additional Testing on Shield

Clean profile ### Restart browser and verify updated shield settings retained
Case 1: Browser restart retain the updated site specific shield settings_PASSED **_Trackers & ads blocking_** Case 1: 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block trackers and ads` to `Aggressive` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined Case 2: 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Aggressive` to `Block trackers and ads` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined Case 3: 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block trackers and ads` to `Allow all trackers and ads` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined **_Block fingerprinting_** Case 1: 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block fingerprinting` to `Aggressive` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined Case 2: 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Aggressive` to `Block fingerprinting` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined Case 3: 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block fingerprinting` to `Allow fingerprinting` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined **_Block cookies_** Case 1: 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block cross site cookies` to `Block all cookies` 5. Restart the browser 6. Open the site shield settings, updated cookies settings are not reatined, encountered https://github.com/brave/brave-browser/issues/24221 Case 2: 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block all cookies` to `Allow all cookies` 5. Restart the browser 6. Open the site shield settings, updated cookies settings are not reatined, encountered https://github.com/brave/brave-browser/issues/24221 Case 3: 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Allow all cookies` to `Block cross site cookies` 5. Restart the browser 6. Open the site shield settings, updated cookies settings are not reatined, encountered https://github.com/brave/brave-browser/issues/24221
Case 2: Browser restart retain the updated global shield settings_PASSED **_Trackers & ads blocking_** Case 1: 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the trackers and ad blocking default settings from `Standard` to `Aggressive` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined Case 2: 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the trackers and ad blocking default settings from `Aggressive` to `Disabled` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined Case 3: 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the trackers and ad blocking default settings from `Disabled` to `Standard` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined **_Fingerprint blocking_** Case 1: 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the fingerprinting default settings from `Standard` to `Strict, may break sites` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined Case 2: 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the fingerprinting default settings from `Strict, may break sites` to `Disabled` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined Case 3: 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the fingerprinting default settings from `Disabled` to `Standard` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined **_Cookies blocking_** Case 1: 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the cookies default settings from `Only cross site` to `All` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined Case 2: 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the cookies default settings from `All` to `Disabled` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined Case 3: 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the cookies default settings from `Disabled` to `Only cross sites` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined
### Site shield settings in Private window
Case 1: Per site shiled settings are propagated to private windows_PASSED - Clean profile 1.42.x - Open a site cnn.com in the normal window - Change the local site shield settings for the site cnn.com - 1. `Block the scripts` 2. `Aggressively block trackers and ads` 3. `Block fingerprinting` 4. `Block cross-site cookies` - Open the private window and open cnn.com - Confirmed the CNN site shield settings are retained in the Private tab Normal window | Private window ----- | ----- ![image](https://user-images.githubusercontent.com/38657976/163396949-392a526e-19d2-4eec-9742-de792b907cfb.png) | ![image](https://user-images.githubusercontent.com/38657976/163397058-7777d3a5-5cec-4454-aa25-dacac87d462a.png)
Case 2: Updated global shiled settings are propagated to Private windows_PASSED - Clean profile 1.42.x - Open a site cnn.com in the normal window - Change the global shield settings - Open a site A and confirmed global shield settings are retained in the normal window - Open the private window and open a site A - Confirmed that the global shield settings are retained in the Private tab
Case 3: Verify that updated per site shield settings in Private window are NOT propagated to Normal window_PASSED - Make changes to shield settings in the Private tab (e.g Allow ads and trackers) - Go to the normal window and open CNN.com and confirm shield settings changes are NOT retained in the normal window Private window | Normal window ---- | ---- ![image](https://user-images.githubusercontent.com/38657976/163397520-e07754b0-16da-49f5-aa1f-81fd883a56cb.png) | ![image](https://user-images.githubusercontent.com/38657976/163397595-42f3fed9-272f-4c4c-b29c-058895a5090f.png)
### Verify disable per site shield settings propagated to all the tabs
Case 1: Disable local shield settings for a site A_PASSED - Clean profile 1.42.x - Open any website A in tab 1 - Disable the default site shield settings for Adblock, Fingerprint, and block cookies (allow all the settings) - Make sure disabled site settings are retained for the site A in tab 1 - Open site A in tab2 - Confirmed that updated site shield settings are retained in tab 2 for the site A
Case 2: Disable global shield settings for a site A_PASSED - Clean profile 1.42.x - Open global shield settings and disable the default global shield settings (allow all the settings) - Open any website A in tab 1 - Make sure disabled global shield settings are retained for the site A in tab 1 - Open site A in tab 2 - Confirmed that disabled global shield settings are retained in tab 2 for the site A
Case 3: Turn OFF the per site shield switch_PASSED - Clean profile 1.42.x - Open any website A in tab 1 - Disable the shield switch - Make sure disabled settings are retained for the site A in tab 1 - Open site A in tab2 - Confirmed that disabled site shield settings are retained in tab 2 for the site A
### Verify disable per site shield settings propagated to all the windows
Case 1: Disable local shield settings for a site A in window 1_PASSED - Clean profile 1.42.x - Open any website A in win 1 - Disable the default site shield settings for Adblock, Fingerprint, and block cookies (allow all the settings) - Make sure updated site shield settings are retained for the site A in win 1 - Open site A in win 2 - Confirmed that disabled site shield settings are retained in win 2 for the site A
Case 2: Disable global shield settings for a site A_ in windows 1_PASSED - Clean profile 1.42.x - Open global shield settings and disable the default global shield settings (allow all the settings) - Open any website A in win 1 - Make sure disabled global shield settings are retained for the site A in win 1 - Open site A in win 2 - Confirmed that disabled global shield settings are retained in win 2 for the site A
Case 3: Turn OFF the per site shield switch_PASSED - Clean profile 1.42.x - Open any website A in win 1 - Disable the shield switch - Make sure disabled settings are retained for the site A in win 1 - Open site A in win 2 - Confirmed that disabled site shield settings are retained in win 2 for the site A
### Verify change per site shield settings propagated to all the tabs
Case 1: Change local shield settings for a site A_PASSED - Clean profile 1.42.x - Open any website A in tab 1 - Change the default site shield settings for Adblock, Fingerprint, and block cookies - Make sure changed site settings are retained for the site A in tab 1 - Open site A in tab2 - Confirmed that updated site shield settings are retained in tab 2 for the site A
Case 2: Changed global shield settings for a site A_PASSED - Clean profile 1.42.x - Open global shield settings and disable the default global shield settings - Open any website A in tab 1 - Make sure changed global shield settings are retained for the site A in tab 1 - Open site A in tab 2 - Confirmed that changed global shield settings are retained in tab 2 for the site A
### Verify change per site shield settings propagated to all the windows
Case 1: Change local shield settings for a site A_PASSED - Clean profile 1.42.x - Open any website A in win 1 - Change the default local shield settings for Adblock, Fingerprint, and block cookies - Make sure per site shield settings are retained for the site A in win 1 - Open site A in win 2 - Confirmed that per site shield settings are retained in win 2 for the site A
Case 2: Changed global shield settings for a site A_PASSED - Clean profile 1.42.x - Open any website A in win 1 - Change the default global shield settings for Adblock, Fingerprint, and block cookies - Make sure changed global shield settings are retained for the site A in win 1 - Open site A in win 2 - Confirmed that changed global shield settings are retained in win 2 for the site A
### Verify `Show the number of blocked items on the Shields icon`
Case 1: Disable show the number of blocked items on the Shields icon settings propagated to all the tabs_PASSED - Clean profile 1.42.x - Open brave://settings/shields - Turn off the `Show the number of blocked items on the Shields icon` switch - Open a site A in tab 1 - Ensured the number of blocked items is NOT shown on the shield in the tab 1 - Open a site A in tab 2 - Ensured the number of blocked items is NOT shown on the shield in the tab 2
Case 2: Disable show the number of blocked items on the Shields icon settings propagated to all the windows_PASSED - Clean profile 1.42.x - Open brave://settings/shields - Turn off the `Show the number of blocked items on the Shields icon` switch - Open a site A in win 1 - Ensured the number of blocked items is NOT shown on the shield in the win 1 - Open a site A in win 2 - Ensured the number of blocked items is NOT shown on the shield in the win 2
Case 3: Disable show the number of blocked items on the Shields icon settings propagated to private windows_PASSED - Clean profile 1.42.x - Open brave://settings/shields - Turn off the `Show the number of blocked items on the Shields icon` switch - Open a site A in the normal window - Ensured the number of blocked items is NOT shown on the shield in the normal window - Open a site A in the private window - Ensured the number of blocked items is NOT shown on the shield in the private window
Upgrade profile
Case 1: Install 1.37.x (version before v2 shield implementation) upgrade it to 1.42.x - PASSED **Case 1.1:** Default shield settings upgrade - PASSED 1. Clean profile 1.37.x 8. Open a few websites 9. Open brave://settings/help 10. Upgrade the profile to 1.42.x 11. Confirmed profile is upgraded to 1.42.x 12. Confirmed default shield settings are retained **Case 1.2:** Update the default shield settings and then upgrade - PASSED 1. Clean profile 1.37.x 2. Open a few websites 3. Edit the site-specific shield settings 5. Open brave://settings/help 6. Upgrade the profile to 1.42.x 8. Confirmed profile is upgraded to 1.42.x 13. Confirmed that updated shield settings are retained after the upgrade **Case 1.3:** Update the global default shield settings and then upgrade - PASSED 1. Clean profile 1.37.x 2. Open a few websites 3. Edit the global shield settings via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 9. Confirmed that updated global shield settings are retained after the upgrade **Case 1.4:** Turn OFF the shield for a few sites and then upgrade - PASSED 1. Clean profile 1.37.x 2. Open a few websites 3. Turn OFF the shield for a few sites via panel 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that shield settings are retained after the upgrade **Case 1.5:** Block scripts and then upgrade - PASSED 1. Clean profile 1.37.x 2. Open a few websites 3. Block scripts for any of the sites via Panel or via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that scrpit block settings are retained after the upgrade **Case 1.6:** Block HTTPS upgrade and then upgrade - PASSED 1. Clean profile 1.37.x 2. Open a few websites 3. Block HTTPS upgrade via Panel or via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that block HTTPS upgrade settings are retained after the upgrade
Case 2: Install 1.38.x (version v2 shield implemented) upgrade it to 1.42.x - PASSED **Case 2.1:** Default shield settings upgrade - PASSED 1. Clean profile 1.38.x 2. Open a few websites 3. Open brave://settings/help 4. Upgrade the profile to 1.42.x 5. Confirmed profile is upgraded to 1.42.x 6. Confirmed default shield settings are retained **Case 2.2:** Update the default shield settings and then upgrade - PASSED 1. Clean profile 1.38.x 2. Open a few websites 3. Edit the site-specific shield settings 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that updated shield settings are retained after the upgrade **Case 2.3:** Update the global default shield settings and then upgrade - PASSED 1. Clean profile 1.38.x 2. Open a few websites 3. Edit the global shield settings via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that updated global shield settings are retained after the upgrade **Case 2.4:** Turn OFF the shield for a few sites and then upgrade - PASSED 1. Clean profile 1.38.x 2. Open a few websites 3. Turn OFF the shield for a few sites via panel 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that shield settings are retained after the upgrade **Case 2.5:** Block scripts and then upgrade - PASSED 1. Clean profile 1.38.x 2. Open a few websites 3. Block scripts for any of the sites via Panel or via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that script block settings are retained after the upgrade **Case 2.6:** Block HTTPS upgrade and then upgrade - PASSED 1. Clean profile 1.38.x 2. Open a few websites 3. Block HTTPS upgrade via Panel or via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that block HTTPS upgrade settings are retained after the upgrade
Case 3: Install 1.41.x and upgrade it to 1.42.x - PASSED **Case 3.1:** Default shield settings upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Open brave://settings/help 4. Upgrade the profile to 1.42.x 5. Confirmed profile is upgraded to 1.42.x 6. Confirmed default shield settings are retained **Case 3.2:** Update the default shield settings and then upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Edit the site-specific shield settings 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that updated shield settings are retained after the upgrade **Case 3.3:** Update the global default shield settings and then upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Edit the global shield settings via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that updated global shield settings are retained after the upgrade **Case 3.4:** Turn OFF the shield for a few sites and then upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Turn OFF the shield for a few sites via panel 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that shield settings are retained after the upgrade **Case 3.5:** Block scripts and then upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Block scripts for any of the sites via Panel or via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that script block settings are retained after the upgrade **Case 3.6:** Block HTTPS upgrade and then upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Block HTTPS upgrade via Panel or via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that block HTTPS upgrade settings are retained after the upgrade
LaurenWags commented 2 years ago

Verification in progress with

Brave | 1.42.78 Chromium: 103.0.5060.134 (Official Build) beta (x86_64)
-- | --
Revision | 8ec6fce403b3feb0869b0732eda8bd95011d333c-refs/branch-heads/5060@{#1262}
OS | macOS Version 12.5 (Build 21G72)

Verified Test Plan areas as per https://github.com/brave/brave-browser/issues/23285#issue-1262768322

Case 1 : Verify Shield v2 UI and controls - PASSED - Confirmed that `shield v1` is not present even behind the `brave://flags` - Confirmed shield v1 code is removed from 1.42.x - Confirmed that clicking on shield on any site opens up `shield v2` - Confirmed that `controls on the shield v2` are shown correctly when the shield is UP - Confirmed that clicking on the controls `Filter lists` redirected to the custom filter page - Confirmed that clicking on the `Global defaults` in the shield redirects to the global shield settings page - Confirmed that clicking on the ads and trackers count opens up the panel with blocked scripts/content - Confirmed that `controls on the shield v2` are shown correctly when the shield is DOWN - Confirmed that trackers count is NOT shown on the shield v2 when the shield is DOWN - Confirmed that clicking on the `Learn more` and `Report site` are redirected to the intended pages when the shield is DOWN brave://flags comparison 1.41.x | 1.42.x -- | -- 1 41 x flags | 1 42 x flags Example | Example | Example | Example | Example | Example -- | -- | -- | -- | -- | -- 1 | 2 | 3 | 4 | 5 | 6
Case 2 : Verify Cosmetic filtering - PASSED Case 1: Clean profile - Ensured custom filter is working as expected
Followed test case similar to that of https://github.com/brave/brave-browser/issues/17910#issuecomment-1155703659: ### Steps: 1. Install 2. Launch brave 3. Visit `https://filterlists.com` 4. Click filter icon on the `Syntaxes` column to select `Adblock Plus` lists. 5. Click on the `blue (i)` icon for `AakList (Anti-Adblock Killer)` 6. Click `View` button in the info panel to the right. 7. Page opens in a new tab and note down the `Title` or `Homepage`: `Title`: `AakList (Anti-Adblock Killer)` `Homepage`:` https://github.com/reek/anti-adblock-killer/` 8. Copy the URL `https://raw.githubusercontent.com/reek/anti-adblock-killer/master/anti-adblock-killer-filters.txt` 9. Visit `brave://settings/shields/filters` 10. Paste above URL in the ` Add custom filter lists` input field 11. Click `Add` button 12. A new list subscription is created URL is added to `Custom lists` area and shows `Last Updated` time 13. Visit `brave://local-state` 14. Search for `AakList (Anti-Adblock Killer)` 15. The new subscription should be listed and the list matches to entry from `https://filterlists.com` Step 6 | Step 7 | Step 12 | Step 14 & 15 ---|---|---|--- 6 | 7 | 12 | 15
- Open any site and click on any object/element on the UI and select the `Block element` context menu and ensure that the element gets blocked on the UI - Remove custom filters and reload the page restores the blocked content on the UI/page. Currently, a browser restart is required to restore the blocked content which is known, encountered #21797 - Select `Manage custom filters` on PT/TOR window is causing the brave crash, encountered https://github.com/brave/brave-browser/issues/24086#issuecomment-1189367310 - Confirmed that element/object can be blocked on the Guest window, but removing custom filter doesn't restore the blocked element on the page, required browser restart but the user will lose the browser session and it's of no use restoring the blocked content, added comments in https://github.com/brave/brave-browser/issues/21797#issuecomment-1189948905 Case 2: Upgrade profile - Install `1.41.100` release build, open a few websites and block the contents on the webpages and ensured elements are blocked - Close browser, rename profile to "upgrade" to 1.42.x beta - Open brave://settings/shields/filters and ensured blocked elements are still present in the custom filters section - Open webpages and ensured elements/objects are still blocked on the UI - Remove the blocked content from brave://settings/shields/filters - Restart the browser and ensued blocked elements are restored on the webpages **_1.41.88_** | **_1.42.65_** -- | -- 1 41 100 | 1 42 78
Case 3 : WDP - PASSED - Verified WDP scenarios and ensured WDP works fine
**`Test Case #1`** - `SE other than Brave` - PASSED * launched 1.42.x * changed the SE default to `Bing` via `brave://settings/search` * visited `brave://prefs-internals` and ensured that `"brave_search_visit_count": 0` * opened https://search.brave.com via new tabs 10 times * refreshed a single tab that has https://search.brave.com opened ~15 times * ensured that `"brave_search_visit_count": 0` under `brave://prefs-internals` **`Test Case #2`** - `Brave as default SE (opening new tabs)` - PASSED * launched 1.42.x * ensured that `Brave` is the SE via `brave://settings/search` * opened `https://search.brave.com` in `3` new tabs and ensured that the `WDP` modal appeared without any isssues (3) * dismissed the modal using the `No Thanks` button * ensured that `"brave_search_visit_count": 3` via `brave://prefs-internals` * opened `https://search.brave.com` in `7` new tabs and ensured that the `WDP` modal appeared without any isssues (10) * ensured that clicking on `Learn More` opens https://brave.com/privacy/browser/#web-discovery-project in a new tab * ensured that `"brave_search_visit_count": 10` via `brave://prefs-internals` * dismissed the modal using the `No Thanks` button * opened `https://search.brave.com` in `10` new tabs and ensured that the `WDP` modal appeared without any isssues (20) * dismissed the modal using the `X` button * ensured that `"brave_search_visit_count": 20` via `brave://prefs-internals` * opened another ~30 tabs with https://search.brave.com and ensured the modal isn't being displayed again **`Test Case #3`** - `Brave as default SE (Refreshing Tab)` - PASSED * launched 1.42.x * ensured that `Brave` is the SE via `brave://settings/search` * opened `https://search.brave.com` in a single tab * refreshed the same tab `2` times and ensured that the `WDP` modal appeared without any issues (3) * dismissed the modal using the `No Thanks` button * refreshed the same tab `7` times and ensured that the `WDP` modal appeared without any issues (10) * dismissed the modal using the `X` button * refreshed the same tab `10` times and ensured that the `WDP` modal appeared without any issues (20) **`Test Case #4`** - `Brave as default SE (Duplicating Tabs)` - PASSED * launched 1.42.x * ensured that `Brave` is the SE via `brave://settings/search` * opened `https://search.brave.com` in a single tab * duplicated the tab `2` times and ensured that the `WDP` modal appeared without any issues (3) * dismissed the modal using the `X` button * duplicated the tab `7` times and ensured that the `WDP` modal appeared without any issues (10) * dismissed the modal using the `No Thanks` button * duplicated the tab `10` times and ensured that the `WDP` modal appeared without any issues (20) **`Test Case #5`** - `Enabling WDP` - PASSED * launched 1.42.x * ensured that `Brave` is the SE via `brave://settings/search` * went through the above cases and ensured that clicking on `Turn on` correctly enabled `WDP` via `brave://settings/search` on `3`, `10` & `20` * ensured that once `WDP` is enabled, the modal isn't being displayed again (example, accept on `3` and open `10` & `20` and ensure the modal isn't being displayed) * ensured that `"brave_search_visit_count"` stays at `3` if `WDP` was enabled on the first modal * ensured that `"brave_search_visit_count"` stays at `10` if `WDP` was enabled on the second modal * ensured that `"brave_search_visit_count"` stays at `20` if `WDP` was enabled on the third modal **`Test Case #6`** - `No Thanks` - PASSED * launched 1.42.x * ensured that `Brave` is the SE via `brave://settings/search` * went through the above cases and ensured that selecting `Don't ask again` stops displaying the modal on `10` & `20` * ensured that dismissing the modal via `X` & `No Thanks` works correctly when `Don't ask again` has been selected * ensured that `"brave_search_visit_count"` stays at `3` if `Don't ask again` was selected and the modal dismissed * ensured that `"brave_search_visit_count"` stays at `10` if `Don't ask again` was selected and the modal dismissed

Additional Testing on Shields

Clean profile - PASSED #### Restart browser and verify updated shield settings retained - PASSED
Case 1: Browser restart retain the updated site specific shield settings - PASSED **_Trackers & ads blocking_** Case 1: PASSED 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block trackers and ads` to `Aggressive` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are retained Case 2: PASSED 1. Continue from Case 1 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Aggressive` to `Block trackers and ads` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are retained Case 3: PASSED 1. Continue from Case 2 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block trackers and ads` to `Allow all trackers and ads` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are retained **_Block fingerprinting_** Case 1: PASSED 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block fingerprinting` to `Aggressive` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are retained Case 2: PASSED 1. Continue from Case 1 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Aggressive` to `Block fingerprinting` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are retained Case 3: PASSED 1. Continue from Case 2 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block fingerprinting` to `Allow fingerprinting` 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are retained **_Block cookies_** Case 1: PASSED 1. Clean profile 1.42.x 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block cross site cookies` to `Block all cookies` 5. Restart the browser 6. Open the site shield settings, updated cookies settings are retained Case 2: PASSED 1. Continue from Case 1 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Block all cookies` to `Allow all cookies` 5. Restart the browser 6. Open the site shield settings, updated cookies settings are retained Case 3: PASSED 1. Continue from Case 2 2. Open a site 3. Click on the site shield settings 4. Change the trackers and ad blocking settings from `Allow all cookies` to `Block cross site cookies` 5. Restart the browser 6. Open the site shield settings, updated cookies settings are retained
Case 2: Browser restart retain the updated global shield settings - PASSED **_Trackers & ads blocking_** Case 1: PASSED 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the trackers and ad blocking default settings from `Standard` to `Aggressive` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined Case 2: PASSED 1. Continue from Case 1 2. Navigate to brave://settings/shields 3. Change the trackers and ad blocking default settings from `Aggressive` to `Disabled` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined Case 3: PASSED 1. Continue from Case 2 2. Navigate to brave://settings/shields 3. Change the trackers and ad blocking default settings from `Disabled` to `Standard` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured trackers and ad blocking settings are reatined **_Fingerprint blocking_** Case 1: PASSED 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the fingerprinting default settings from `Standard` to `Strict, may break sites` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined Case 2: PASSED 1. Continue from Case 1 2. Navigate to brave://settings/shields 3. Change the fingerprinting default settings from `Strict, may break sites` to `Disabled` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined Case 3: PASSED 1. Continue from Case 2 2. Navigate to brave://settings/shields 3. Change the fingerprinting default settings from `Disabled` to `Standard` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined **_Cookies blocking_** Case 1: PASSED 1. Clean profile 1.42.x 2. Navigate to brave://settings/shields 3. Change the cookies default settings from `Only cross site` to `All` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined Case 2: PASSED 1. Continue from Case 1 2. Navigate to brave://settings/shields 3. Change the cookies default settings from `All` to `Disabled` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined Case 3: PASSED 1. Continue from Case 2 2. Navigate to brave://settings/shields 3. Change the cookies default settings from `Disabled` to `Only cross sites` 4. Open a site and click on shield and ensured global shield settings are applied 5. Restart the browser 6. Open the site shield settings and ensured fingerprinting settings are reatined
Upgrade profile - PASSED
Case 3: Install 1.41.x and upgrade it to 1.42.x - InProgress **Case 3.1:** Default shield settings upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Open brave://settings/help 4. Upgrade the profile to 1.42.x 5. Confirmed profile is upgraded to 1.42.x 6. Confirmed default shield settings are retained **Case 3.2:** Update the default site specific shield settings and then upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Edit the site-specific shield settings 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that updated shield settings are retained after the upgrade **Case 3.3:** Update the global default shield settings and then upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Edit the global shield settings via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that updated global shield settings are retained after the upgrade **Case 3.4:** Turn OFF the shield for a few sites and then upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Turn OFF the shield for a few sites via panel 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that shield settings are retained after the upgrade **Case 3.5:** Block scripts and then upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Block scripts for any of the sites via Panel or via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that script block settings are retained after the upgrade **Case 3.6:** Block HTTPS upgrade and then upgrade - PASSED 1. Clean profile 1.41.x 2. Open a few websites 3. Block HTTPS upgrade via Panel or via brave://settings/shields 4. Open brave://settings/help 5. Upgrade the profile to 1.42.x 6. Confirmed profile is upgraded to 1.42.x 8. Confirmed that block HTTPS upgrade settings are retained after the upgrade
btlechowski commented 2 years ago

Verification passed on

Brave 1.42.78 Chromium: 103.0.5060.134 (Official Build) beta (64-bit)
Revision 8ec6fce403b3feb0869b0732eda8bd95011d333c-refs/branch-heads/5060@{#1262}
OS Ubuntu 18.04 LTS

Verified Test Plan areas as per https://github.com/brave/brave-browser/issues/23285#issue-1262768322

Case 1 : Verify Shield v2 UI and controls - PASSED - Confirmed that `shield v1` is not present even behind the `brave://flags` - Confirmed shield v1 code is removed from 1.42.x - Confirmed that clicking on shield on any site opens up `shield v2` - Confirmed that `controls on the shield v2` are shown correctly when the shield is UP - Confirmed that clicking on the controls `Filter lists` redirected to the custom filter page - Confirmed that clicking on the `Global defaults` in the shield redirects to the global shield settings page - Confirmed that clicking on the ads and trackers count opens up the panel with blocked scripts/content - Confirmed that `controls on the shield v2` are shown correctly when the shield is DOWN - Confirmed that trackers count is NOT shown on the shield v2 when the shield is DOWN - Confirmed that clicking on the `Learn more` and `Report site` are redirected to the intended pages when the shield is DOWN brave://flags comparison ![image](https://user-images.githubusercontent.com/34715963/181603256-a211ddd0-b4d8-4a00-ba73-41e63db607d1.png)| ![image](https://user-images.githubusercontent.com/34715963/181603161-7439112d-8e7f-4743-99de-87f8381af889.png) --|-- ![image](https://user-images.githubusercontent.com/34715963/181603346-854afa17-0ac4-4126-8d40-fdc43b70a970.png) ![image](https://user-images.githubusercontent.com/34715963/181603539-f842737f-fb0b-412b-a4ee-647d0e873db8.png) ![image](https://user-images.githubusercontent.com/34715963/181603579-5e8a5650-0fea-4f82-b3d5-f5c87b37ffeb.png) ![image](https://user-images.githubusercontent.com/34715963/181603633-89c6f15a-6cdc-4005-af1a-e0a9e04ecfee.png) ![image](https://user-images.githubusercontent.com/34715963/181603657-0987d900-bfaa-4ba5-9d71-eab6d9beac8a.png) ![image](https://user-images.githubusercontent.com/34715963/181603723-f0157c81-f2b7-49b0-a1ba-366beaf9f7f2.png) ![image](https://user-images.githubusercontent.com/34715963/181603868-62ffc77d-7c66-4fd1-be94-3092922c1402.png) ![image](https://user-images.githubusercontent.com/34715963/181604206-e28786a5-1312-4b2e-ba45-ff17085fc050.png)
Case 2 : Verify Cosmetic filtering - PASSED Case 1: Clean profile - Ensured custom filter is working as expected
Followed test case similar to that of https://github.com/brave/brave-browser/issues/17910#issuecomment-1155703659: ### Steps: 1. Install 2. Launch brave 3. Visit `https://filterlists.com` 4. Click filter icon on the `Syntaxes` column to select `Adblock Plus` lists. 5. Click on the `blue (i)` icon for `AakList (Anti-Adblock Killer)` 6. Click `View` button in the info panel to the right. 7. Page opens in a new tab and note down the `Title` or `Homepage`: `Title`: `AakList (Anti-Adblock Killer)` `Homepage`:` https://github.com/reek/anti-adblock-killer/` 8. Copy the URL `https://raw.githubusercontent.com/reek/anti-adblock-killer/master/anti-adblock-killer-filters.txt` 9. Visit `brave://settings/shields/filters` 10. Paste above URL in the ` Add custom filter lists` input field 11. Click `Add` button 12. A new list subscription is created URL is added to `Custom lists` area and shows `Last Updated` time 13. Visit `brave://local-state` 14. Search for `AakList (Anti-Adblock Killer)` 15. The new subscription should be listed and the list matches to entry from `https://filterlists.com` ![image](https://user-images.githubusercontent.com/34715963/181605067-b6b79ddb-bcaf-4ca3-ae58-a2e7124baa50.png) ![image](https://user-images.githubusercontent.com/34715963/181605169-16fbbe14-7b48-469e-b85b-f382cb7a68bb.png)
- Open any site and click on any object/element on the UI and select the `Block element` context menu and ensure that the element gets blocked on the UI - Remove custom filters and reload the page restores the blocked content on the UI/page. Currently, a browser restart is required to restore the blocked content which is known, encountered #21797 - Select `Manage custom filters` on PT/TOR window is causing the brave crash, encountered https://github.com/brave/brave-browser/issues/24086#issuecomment-1189367310 - Confirmed that element/object can be blocked on the Guest window, but removing custom filter doesn't restore the blocked element on the page, required browser restart but the user will lose the browser session and it's of no use restoring the blocked content, added comments in https://github.com/brave/brave-browser/issues/21797#issuecomment-1189948905 ![image](https://user-images.githubusercontent.com/34715963/181605371-3402ce75-703c-4515-acdb-1a1d5279de29.png) ![image](https://user-images.githubusercontent.com/34715963/181605418-955a0791-fb76-4f0f-a463-cb6c2b21225b.png) Case 2: Upgrade profile - Install `1.41.x` release build, open a few websites and block the contents on the webpages and ensured elements are blocked - Close browser, rename profile to "upgrade" to 1.42.x beta - Open brave://settings/shields/filters and ensured blocked elements are still present in the custom filters section - Open webpages and ensured elements/objects are still blocked on the UI - Remove the blocked content from brave://settings/shields/filters - Restart the browser and ensued blocked elements are restored on the webpages ![image](https://user-images.githubusercontent.com/34715963/181605903-4b1ffb32-f9b7-4f1c-97a7-f6bf4e55fde1.png) ![image](https://user-images.githubusercontent.com/34715963/181605943-d6952300-416d-4865-b928-e0ccb277a45a.png)
Case 3 : WDP - PASSED - Verified WDP scenarios and ensured WDP works fine
**`Test Case #1`** - `SE other than Brave` - PASSED * launched 1.42.x * changed the SE default to `Bing` via `brave://settings/search` * visited `brave://prefs-internals` and ensured that `"brave_search_visit_count": 0` * opened https://search.brave.com via new tabs 10 times * refreshed a single tab that has https://search.brave.com opened ~15 times * ensured that `"brave_search_visit_count": 0` under `brave://prefs-internals` ![image](https://user-images.githubusercontent.com/34715963/181613589-fad78c21-ce28-4229-9c81-bd4d91989666.png) ![image](https://user-images.githubusercontent.com/34715963/181613694-470f533a-d906-4228-bdb1-497f9993d0f8.png) **`Test Case #2`** - `Brave as default SE (opening new tabs)` - PASSED * launched 1.42.x * ensured that `Brave` is the SE via `brave://settings/search` * opened `https://search.brave.com` in `3` new tabs and ensured that the `WDP` modal appeared without any isssues (3) * dismissed the modal using the `No Thanks` button * ensured that `"brave_search_visit_count": 3` via `brave://prefs-internals` * opened `https://search.brave.com` in `7` new tabs and ensured that the `WDP` modal appeared without any isssues (10) * ensured that clicking on `Learn More` opens https://brave.com/privacy/browser/#web-discovery-project in a new tab * ensured that `"brave_search_visit_count": 10` via `brave://prefs-internals` * dismissed the modal using the `No Thanks` button * opened `https://search.brave.com` in `10` new tabs and ensured that the `WDP` modal appeared without any isssues (20) * dismissed the modal using the `X` button * ensured that `"brave_search_visit_count": 20` via `brave://prefs-internals` * opened another ~30 tabs with https://search.brave.com and ensured the modal isn't being displayed again ![image](https://user-images.githubusercontent.com/34715963/181613827-06861d86-468e-4912-a056-a3ca93e49493.png) ![image](https://user-images.githubusercontent.com/34715963/181613907-b1eab8a9-fe16-42d2-9606-78d00089959f.png) ![image](https://user-images.githubusercontent.com/34715963/181614015-294604cd-4127-4f44-9c42-f9f98f218dda.png) **`Test Case #3`** - `Brave as default SE (Refreshing Tab)` - PASSED * launched 1.42.x * ensured that `Brave` is the SE via `brave://settings/search` * opened `https://search.brave.com` in a single tab * refreshed the same tab `2` times and ensured that the `WDP` modal appeared without any issues (3) * dismissed the modal using the `No Thanks` button * refreshed the same tab `7` times and ensured that the `WDP` modal appeared without any issues (10) * dismissed the modal using the `X` button * refreshed the same tab `10` times and ensured that the `WDP` modal appeared without any issues (20) **`Test Case #4`** - `Brave as default SE (Duplicating Tabs)` - PASSED * launched 1.42.x * ensured that `Brave` is the SE via `brave://settings/search` * opened `https://search.brave.com` in a single tab * duplicated the tab `2` times and ensured that the `WDP` modal appeared without any issues (3) * dismissed the modal using the `X` button * duplicated the tab `7` times and ensured that the `WDP` modal appeared without any issues (10) * dismissed the modal using the `No Thanks` button * duplicated the tab `10` times and ensured that the `WDP` modal appeared without any issues (20) **`Test Case #5`** - `Enabling WDP` - PASSED * launched 1.42.x * ensured that `Brave` is the SE via `brave://settings/search` * went through the above cases and ensured that clicking on `Turn on` correctly enabled `WDP` via `brave://settings/search` on `3`, `10` & `20` * ensured that once `WDP` is enabled, the modal isn't being displayed again (example, accept on `3` and open `10` & `20` and ensure the modal isn't being displayed) * ensured that `"brave_search_visit_count"` stays at `3` if `WDP` was enabled on the first modal * ensured that `"brave_search_visit_count"` stays at `10` if `WDP` was enabled on the second modal * ensured that `"brave_search_visit_count"` stays at `20` if `WDP` was enabled on the third modal **`Test Case #6`** - `No Thanks` - PASSED * launched 1.42.x * ensured that `Brave` is the SE via `brave://settings/search` * went through the above cases and ensured that selecting `Don't ask again` stops displaying the modal on `10` & `20` * ensured that dismissing the modal via `X` & `No Thanks` works correctly when `Don't ask again` has been selected * ensured that `"brave_search_visit_count"` stays at `3` if `Don't ask again` was selected and the modal dismissed * ensured that `"brave_search_visit_count"` stays at `10` if `Don't ask again` was selected and the modal dismissed
palianskas commented 2 years ago

Personally I think this was a bad move. The flags to bring back Shields v1 was a remedy for the bad redesign.

tristansly commented 2 years ago

Why on earth did you get rid of being able to change ALL options with ONE click to the shield? AND THEN remove the old and superior one completely!? The new one is worse. Now I'm having to download an older version just to get the shield back... For the third time.

bsclifton commented 2 years ago

@palianskas @tristansly what exactly were you able to do with the older version that you're unable to now? (genuinely curious - more info super appreciated)

I know enabling/disabling specific scripts is affected; for that, you can always check out the NoScript extension. But could you elaborate on your scenario a bit more?

tristansly commented 2 years ago

It adds a unnecessary and pointless click by not exposing the entire "Advanced Menu" when you click the shield. Being as you have to unblock scripts on basically all sites to work, it's adding unnecessary clicks to every new site I visit.

tristansly commented 2 years ago

I am turning off Brave's Shield as it not only has been redesigned to be less efficient, it doesn't seem to work right now as I am having to go to each sites settings and disable javascript manually; using ublock Origin to cover atm. What a pain. You had a good thing for a while!

tristansly commented 2 years ago

@palianskas @tristansly what exactly were you able to do with the older version that you're unable to now? (genuinely curious - more info super appreciated)

I know enabling/disabling specific scripts is affected; for that, you can always check out the NoScript extension. But could you elaborate on your scenario a bit more?

Additionally, I am using Brave so I DON'T have to use NoScript. Additionally, I prefer ublock origin for quite a number of years now. If I have to use NoScript, then I can use whatever browser I want. This is where Brave excelled, but now it seems the devs are making it harder to control permissions by removing granular control over what shield features are activated/deactivated. I don't want to turn the whole shield off, that would be silly if all I need to do is turn scripts off. Why not add an option that makes the whole menu flyout every time?

palianskas commented 2 years ago

With Shield V1, I had setup for it to block all scripts by default and selectively enabling them if I deemed the site actually needed them. As it is now, I have switched to using uBlock Origin's filters, but can't seem to get it configured properly. NoScript seems like a plug-in solution for my use case, however, either because it's something I haven't got used to or because the UI is abhorent (in my opinion), using it isn't optimal compared to Shield V1

bsclifton commented 2 years ago

@tristansly @palianskas thanks for elaborating. An alternative to NoScript would be uMatrix https://chrome.google.com/webstore/detail/umatrix/ogfcmafjalglgifnmanfmnieipoejdcf

The saving of the "Advanced" menu (expanded or collapsed state) has been fixed 👍

pes10k commented 2 years ago

Also, just to give some context to why the per-script controls were removed from Brave in the first place, we decided to remove the feature for three reasons:

  1. Brave shipped a number of other on-by-default privacy features that reduced the privacy-benefit of the per-script-controls. For example, Brave ships ephemeral, partitioned storage and randomized fingerprint protections by default (among many other features) dramatically reducing how much privacy harm most scripts can cause. Thats not to say that per-script controls aren't still useful, just that they're useful in less cases than they were previously.
  2. Chromium internals changed in a way that made maintaining the feature more difficult and costly (at least given the way were were implementing it previously)
  3. We evaluated uMatrix and NoScript and decided they were likely sufficient alternatives for the small number of Brave users who used the per-script controls

However, that being said, we will revisit the feature if we can find an easier way to re-implement given Chromium internals, or if we believe a significant portion of Brave users would use the feature if made available again

FreeBornAngel commented 2 years ago

Please bring back the v1 shields, the alternatives offered are crap and not useful for what the shields were doing.

tristansly commented 2 years ago

Please bring back the v1 shields, the alternatives offered are crap and not useful for what the shields were doing.

Agree hardcore. Brave no fun to use now. Script blockers not fun to use anymore, if ever they were. One click on menu, give me ALL POSSIBLE OPTIONS one menu. NO AVANCED SUBMENU please