Bug 1589407 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Thomas Nguyen (:tnguyen) from comment #1)
> I don't think it is a regression, ReevaluateReferrerAfterTrackingStatusIsKnown only applies to parent and missing an update referrer to child. Seems we are missing that part.

This bug is not related to blacklist/whitelist in the URL Classifier (blacklist/whitelist work normally).

This bug happens because of  `document.referrer` loads ReferrerInfo stored in the content process.
While content creates the ReferrerInfo, it doesn't know if the URL is a tracker or not. The tracking URL is annotated as a tracker in the parent process, and then the parent recomputes its ReferrerInfo. Since we don't sync the new ReferrInfo back to the child process so the result of document.referrer is not trimmed.
Revision 1 by
on 
This bug is not related to blacklist/whitelist in the URL Classifier (blacklist/whitelist work normally).

This bug happens because of  `document.referrer` loads ReferrerInfo stored in the content process.
While content creates the ReferrerInfo, it doesn't know if the URL is a tracker or not. The tracking URL is annotated as a tracker in the parent process, and then the parent recomputes its ReferrerInfo. Since we don't sync the new ReferrInfo back to the child process so the result of document.referrer is not trimmed.

Back to Bug 1589407 Comment 2