Open Bug 1617784 Opened 2 months ago Updated 22 days ago

ContentBlockingAllowListPrincipal lookup doesn't handle ancestors in a different process


(Core :: Privacy: Anti-Tracking, defect, P3)





(Reporter: mattwoodrow, Unassigned)


(Blocks 1 open bug)


ContentBlockingAllowListPrincipal lookup for document loading uses ThirdPartyUtil::GetTopWindowForChannel, which walks up the nsGlobalWindowOuter chain, and can only see Windows that in the current process. With fission, this will frequently not be the full ancestor chain.

As part of bug 1615966, I'm moving the computation of topWindowURI/contentBlockingAllowListPrincipal to the parent-process, when using DocumentChannel for a document load.

This means we should have access to all ancestor WindowGlobalParent's, not just Windows that exist in the current process.

I've had to manually add back support for restricting the lookup to within the current process, because we fail a bunch of tests otherwise:

It would be good to figure out why this, because I suspect we need it in the long term.

Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.