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 unnecessary gets for publisher data #3525

Closed
NejcZdovc opened this issue Feb 28, 2019 · 1 comment · Fixed by brave/brave-core#1822
Closed

Remove unnecessary gets for publisher data #3525

NejcZdovc opened this issue Feb 28, 2019 · 1 comment · Fixed by brave/brave-core#1822

Comments

@NejcZdovc
Copy link
Contributor

Now that we update % based on normalize observer (done here brave/brave-core#1780), we don't need to get publisher data anymore if panel is opened for the same publisher. We only need to get data if publisher is different

@NejcZdovc NejcZdovc self-assigned this Feb 28, 2019
@NejcZdovc NejcZdovc added the priority/P5 Not scheduled. Don't anticipate work on this any time soon. label Mar 1, 2019
NejcZdovc added a commit to brave/brave-core that referenced this issue Mar 2, 2019
@NejcZdovc NejcZdovc added this to the 0.63.x - Nightly milestone Mar 4, 2019
@btlechowski
Copy link

btlechowski commented Mar 14, 2019

Verification passed on

Brave 0.63.4 Chromium: 73.0.3683.67 (Official Build) dev (64-bit)
Revision a83fd4f3207ae83412d329a9ca1239dd1e068345-refs/branch-heads/3683@{#760}
OS Windows 7 Service Pack 1 Build 7601.24312

Used test plan from brave/brave-core#1822

Verification passed on

Brave 0.63.12 Chromium: 73.0.3683.75 (Official Build) dev (64-bit)
Revision 909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS Linux

Verified passed with

Brave 0.63.14 Chromium: 73.0.3683.75 (Official Build) dev(64-bit)
Revision 909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS Mac OS X

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants