Open Bug 1442710 Opened 6 years ago Updated 2 years ago

[tracking protection 2.0] whitelist in private mode needs to be in-memory only

Categories

(Firefox for iOS :: General, defect, P3)

Product:
Firefox for iOS
Component:
General
Platform:
Other
iOS
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
fxios + ---

People

(Reporter: garvan, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #1442649 +++
I don't see this safely landing for 11.0.

Because we changed implementation to have content blocker API do the whitelisting, rather than doing it in our code on WKWebView navigation notifications, we would either have to:
- re-parse the content blocking lists when entering/exiting PB mode
- keep parsed copies of the lists in-memory in the WKWebView process. 

The first has a performance cost, the second has a memory cost. 
The blocking lists on-disk are 1 MB.

[ WIP patch for my reference https://github.com/garvankeeley/firefox-ios/commit/f160475dbb2bcba280ce2ef7edd13cb06386a370 ]
This may be a compelling reason to change the blocklist implementation to use the same on/off mechanism as we use for disabling in pref or reload, it just needs to be hooked up to WKWebView navigation.
Priority: P2 → P3
Marked as 'tracking +' while we wait for more feedback on this feature
tracking-fxios: 11.0 → +
Assignee: gkeeley → nobody
Status: ASSIGNED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.