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

GH-1621: Site-Specific Whitelisting for Unknown Trackers via Anti-Tracking #417

Merged
merged 21 commits into from Jul 24, 2019

Conversation

@Eden12345
Copy link
Contributor

@Eden12345 Eden12345 commented Jul 18, 2019

JIRA Ticket: https://cliqztix.atlassian.net/browse/GH-1621

Notes
If you need more test cases, turn off Ad-Blocking and head to any news site like cnn.com

The race condition issue should be fixed along with a few other issues that @IAmThePan found, and I also have moved the strings into the translation library. It should be good to go at this point

Eden12345 and others added 14 commits Jun 4, 2019
… on further commits until Design is finished reviewing the feature (a console.log has been added in each place where logic may be added to match upcoming feature implementation requirements)
@Eden12345 Eden12345 requested review from christophertino and wlycdgr Jul 18, 2019
@Eden12345 Eden12345 requested review from zarembsky and ghostery/ghostery as code owners Jul 18, 2019
@christophertino christophertino added this to the 8.4.1 milestone Jul 19, 2019
Copy link
Member

@jsignanini jsignanini left a comment

@Eden12345 looks like opening the Settings view from the Panel is broken (shows blank). See the error logs in the panel's console log.

blocked: false,
catId: 'anti_tracking_unknown',
description: '',
id: 100000000 + idx,

This comment has been minimized.

@Eden12345

Eden12345 Jul 23, 2019
Author Contributor

Remove this line along with any other props that are unnecessary for the <Tracker /> component for Unknown trackers

This comment has been minimized.

@Eden12345

Eden12345 Jul 23, 2019
Author Contributor

Edit: We still need a unique ID for this because it's used later as a React key prop when rendering all the trackers from the <Trackers /> component. I'll use the unknownTracker.name and concatenate it with the first domain listed in the unknownTracker.domains array (if the array is empty, it will just concatenate "undefined" onto the string).

…ccasional bug with unwhitelisting
@jsignanini jsignanini merged commit a325caf into develop Jul 24, 2019
2 checks passed
2 checks passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@jsignanini jsignanini deleted the feature/anonymizedDataPointsCategory branch Jul 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants