Separate BTP user interaction tracking from ContentBlockingUserInteraction
Categories
(Core :: Privacy: Anti-Tracking, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: pbz, Assigned: pbz)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files)
We have RecordUserActivationForBTP
on PWindowGlobal
now so it should be relatively easy to add our own call coming from the Document on user activation.
Separating the messages makes the code more maintainable and easier to read. It also allows us to solve a shortcoming of the existing user interaction code which doesn't correctly record user activation for the top level if the user interacts with the iframe.
The spec describes this attribution to the top level site host in the algorithm here: https://privacycg.github.io/nav-tracking-mitigations/#bounce-tracking-mitigations-activation-monkey-patch
Assignee | ||
Updated•4 months ago
|
Assignee | ||
Comment 1•3 months ago
|
||
Assignee | ||
Comment 2•3 months ago
|
||
Comment 4•3 months ago
|
||
Backed out for causing bustages on BounceTrackingProtection.h
Assignee | ||
Comment 5•3 months ago
|
||
Thanks! That's a non-unified build failure. I think BounceTrackingProtection.h
is missing a forward declaration of WindowContext
. Should be easy to fix.
https://hg.mozilla.org/mozilla-central/rev/c0c1a4858111
https://hg.mozilla.org/mozilla-central/rev/38f8fb84e7c2
Description
•