Skip to content
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

Remove chrome-browser-browsing_data-chrome_browsing_data_remover_delegate_factory.cc.patch #14819

Closed
mariospr opened this issue Mar 18, 2021 · 2 comments

Comments

@mariospr
Copy link
Contributor

Description

This patch could be removed in favour of a chromium_src override that would define its own version of ChromeBrowsingDataRemoverDelegateFactory::BuildServiceInstanceFor() to simply return an instance of BraveBrowsingDataRemoverDelegate(), instead of patching the original method from upstream (which doesn't do anything else other than returning an instance of ChromeBrowsingDataRemoverDelegate).

Brave version (brave://version info)

Brave 1.24.2 (Chromium 89.0.4389.90)

Miscellaneous Information:

This removal references a patch initially introduced with #8231 (and later modified for #8826) so please use the test plan detailed in brave/brave-core#4624 for QA purposes (i.e. check that things continue to work).

@mariospr mariospr added this to the 1.24.x - Nightly milestone Mar 18, 2021
@mariospr mariospr self-assigned this Mar 18, 2021
mariospr added a commit to brave/brave-core that referenced this issue Mar 18, 2021
…gate_factory.cc.patch

This patch could be removed in favour of a chromium_src override that
would define its version of ChromeBrowsingDataRemoverDelegateFactory's
BuildServiceInstanceFor() to simply return an instance of
BraveBrowsingDataRemoverDelegate(), instead of patching the original
method from upstream (which doesn't do anything else other than
returning an instance of ChromeBrowsingDataRemoverDelegate).

Resolves brave/brave-browser#14819
mariospr added a commit to brave/brave-core that referenced this issue Mar 22, 2021
…gate_factory.cc.patch

This patch could be removed in favour of a chromium_src override that
would define its version of ChromeBrowsingDataRemoverDelegateFactory's
BuildServiceInstanceFor() to simply return an instance of
BraveBrowsingDataRemoverDelegate(), instead of patching the original
method from upstream (which doesn't do anything else other than
returning an instance of ChromeBrowsingDataRemoverDelegate).

Resolves brave/brave-browser#14819
@mariospr
Copy link
Contributor Author

mariospr commented Apr 9, 2021

Closing as per review comments in the associated PR

@mariospr mariospr closed this as completed Apr 9, 2021
@stephendonner stephendonner added the QA/In-Progress Indicates that QA is currently in progress for that particular issue label Apr 15, 2021
@stephendonner
Copy link

stephendonner commented Apr 15, 2021

Verified PASSED using testplans from both #8231 and #8826

Brave 1.24.65 Chromium: 90.0.4430.72 (Official Build) dev (x86_64)
Revision b6172ef8d07ef486489a4b11b66b2eaeed50d132-refs/branch-heads/4430@{#1233}
OS macOS Version 11.2.3 (Build 20D91)

Confirmed that the UI reads Site and Shields Settings in brave://settings/clearBrowserData

Steps:

  1. Launched Brave with a new profile
  2. Loaded brave.com and changed Cross-site cookies blocked to Cookies blocked via the Shields panel
  3. Launched the Clear Browsing data dialog via brave://settings/clearBrowserData
  4. Confirmed that Site Settings has 1 Site as a label with the Last hour time range
  5. Clicked the Clear data button and checked that the label is now None
  6. Loaded brave.com and confirmed that Cross-site cookies blocked is now restored as the default in the Shields settings
example example example example
Screen Shot 2021-04-15 at 2 23 36 PM Screen Shot 2021-04-15 at 2 14 13 PM Screen Shot 2021-04-15 at 2 14 57 PM Screen Shot 2021-04-15 at 2 15 28 PM

Verification passed on

Brave 1.24.66 Chromium: 90.0.4430.72 (Official Build) beta (64-bit)
Revision b6172ef8d07ef486489a4b11b66b2eaeed50d132-refs/branch-heads/4430@{#1233}
OS Ubuntu 18.04 LTS

Verified test plan from #8231 and #8826

Verification

changed Cross-site cookies blocked to Cookies blocked via the Shields panel
image
Confirmed that Site Settings has 1 Site as a label with the Last hour time range in brave://settings/clearBrowserData
image
Confirmed that Site Settings has None as a label with the Last hour time range in brave://settings/clearBrowserData after clearing data
image
confirmed that Cross-site cookies blocked is now restored as the default in the Shields settings
image


Verification passed on

Brave | 1.24.69 Chromium: 90.0.4430.72 (Official Build) dev (64-bit)
-- | --
Revision | b6172ef8d07ef486489a4b11b66b2eaeed50d132-refs/branch-heads/4430@{#1233}
OS | Windows 10 OS Version 2004 (Build 19041.928)

changed Cross-site cookies blocked to Cookies blocked via the Shields panel

Steps:

  1. Launched Brave with a new profile
  2. Loaded brave.com and changed Cross-site cookies blocked to Cookies blocked via the Shields panel
  3. Launched the Clear Browsing data dialog via brave://settings/clearBrowserData
  4. Confirmed that Site Settings has 1 Site as a label with the Last hour time range
  5. Clicked the Clear data button and checked that the label is now None
  6. Loaded brave.com and confirmed that Cross-site cookies blocked is now restored as the default in the Shields settings
image image image image

@stephendonner stephendonner added QA Pass-macOS and removed QA/In-Progress Indicates that QA is currently in progress for that particular issue labels Apr 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment