Selective blocking

[smalluban]

WIP.

Usage of the TrackerException model in the background:

import TrackerException from '/store/tracker-exception.js';

// Resolve a full list of the models
await store.resolve([TrackerException])

// Resolve model by id
// The definition always returns a model with predefined values,
// but they are not saved until there is a `store.set()` call
// Still, I think this case should be used rarely in the BG
await store.resolve(TrackerException, 'trackerId...')

[github-actions]

Builds for commit b0116ee:

• ghostery-chrome-10.2.16-f7c6593
• ghostery-edge-10.2.16-f7c6593
• ghostery-firefox-10.2.16-f7c6593
• ghostery-opera-10.2.16-f7c6593

[github-actions]

Builds for commit b0116ee:

• ghostery-chrome-10.2.16-604a44b
• ghostery-edge-10.2.16-604a44b
• ghostery-firefox-10.2.16-604a44b
• ghostery-opera-10.2.16-604a44b

[github-actions]

Builds for commit 873e2d3:

• ghostery-chrome-10.2.16-b5f40cc
• ghostery-edge-10.2.16-b5f40cc
• ghostery-firefox-10.2.16-b5f40cc
• ghostery-opera-10.2.16-b5f40cc

[github-actions]

Builds for commit 210ae12:

• ghostery-chrome-10.2.16-d63a144
• ghostery-edge-10.2.16-d63a144
• ghostery-firefox-10.2.16-d63a144
• ghostery-opera-10.2.16-d63a144

[github-actions]

Builds for commit e14ce8f:

• ghostery-chrome-10.2.16-205d1f1
• ghostery-edge-10.2.16-205d1f1
• ghostery-firefox-10.2.16-205d1f1
• ghostery-opera-10.2.16-205d1f1

[github-actions]

Builds for commit e6450d6:

• ghostery-chrome-10.2.16-63214fc
• ghostery-edge-10.2.16-63214fc
• ghostery-firefox-10.2.16-63214fc
• ghostery-opera-10.2.16-63214fc

[github-actions]

Builds for commit 4d098ce:

• ghostery-chrome-10.2.16-71af960
• ghostery-edge-10.2.16-71af960
• ghostery-firefox-10.2.16-71af960
• ghostery-opera-10.2.16-71af960

[github-actions]

Builds for commit 726c768:

• ghostery-chrome-10.2.16-32ebc87
• ghostery-edge-10.2.16-32ebc87
• ghostery-firefox-10.2.16-32ebc87
• ghostery-opera-10.2.16-32ebc87

[github-actions]

Builds for commit f6884fb:

• ghostery-chrome-10.2.16-35a61da
• ghostery-edge-10.2.16-35a61da
• ghostery-firefox-10.2.16-35a61da
• ghostery-opera-10.2.16-35a61da

[github-actions]

Builds for commit bf10d74:

• ghostery-chrome-10.2.16-c7177eb
• ghostery-edge-10.2.16-c7177eb
• ghostery-firefox-10.2.16-c7177eb
• ghostery-opera-10.2.16-c7177eb

[chrmod]

Amazing!

I'm all for merging it in this state as it is already too big to handle.

Few things will require to be addressed before it can be released, for example Safari support.

[philipp-classen]

This is a bit of a weird setup, having a domain trusted and blocked at the same time. Is such a case possible to reach in production?

Also, initializing it with each tests, might be easier to read, since it makes the tests stand-alone and independent of each other. If code sharing is the concern, you can use a helper function.

[chrmod]

it is expected to have both blockedDomains and allowedDomains at the same time. In this way we remember the opposite exceptions when users toggle the blocking mode.

[github-actions]

Builds for commit 6d3a812:

• ghostery-chrome-10.2.16-90c8090
• ghostery-edge-10.2.16-90c8090
• ghostery-firefox-10.2.16-90c8090
• ghostery-opera-10.2.16-90c8090