Bugzilla

For manual testing:

Enable the feature by setting `privacy.bounceTrackingProtection.enabled` to `true`

You can observe the state of the two maps via the browser console like so:

```
 let btProtection = Cc[
    "@mozilla.org/bounce-tracking-protection;1"
  ].getService(Ci.nsIBounceTrackingProtection);

// Hosts of the maps are exposed via
btProtection.bounceTrackerCandidateHosts;
btProtection.userActivationHosts
```

Logging can be enabled by running with:
```
MOZ_LOG="BounceTrackingProtection:4"
```
4 = debug is quite noisy, you can also drop that to 3 = info

https://bounce-tracking-demo.glitch.me/ is a good demo site. After going through the redirect flows `btProtection.bounceTrackerCandidateHosts` should be populated. Note that you may have to wait 10 seconds (timeout) for the bounce tracking algorithm to kick in.

For manual testing:

Enable the feature by setting `privacy.bounceTrackingProtection.enabled` to `true`. This requires an application restart.

You can observe the state of the two maps via the browser console like so:

```
 let btProtection = Cc[
    "@mozilla.org/bounce-tracking-protection;1"
  ].getService(Ci.nsIBounceTrackingProtection);

// Hosts of the maps are exposed via
btProtection.bounceTrackerCandidateHosts;
btProtection.userActivationHosts
```

Logging can be enabled by running with:
```
MOZ_LOG="BounceTrackingProtection:4"
```
4 = debug is quite noisy, you can also drop that to 3 = info

https://bounce-tracking-demo.glitch.me/ is a good demo site. After going through the redirect flows `btProtection.bounceTrackerCandidateHosts` should be populated. Note that you may have to wait 10 seconds (timeout) for the bounce tracking algorithm to kick in.