Closed Bug 1600878 Opened 5 years ago Closed 5 years ago

Remove the use of contentBlockingEvent in RemoteSecurityUI

Categories

(Core :: Privacy: Anti-Tracking, task, P1)

task

Tracking

()

RESOLVED FIXED
mozilla74
Tracking Status
firefox74 --- fixed

People

(Reporter: dimi, Assigned: dimi)

References

Details

Attachments

(3 files)

The parent process registers a listener to update contentBlockingEvent to RemoteSecurityUI. In Bug 159904, we plan to store content blocking related stuff in WindowGlobalParent. This allows parent process to access contentBlockingEvent directly via WindowGlobalParent.

This allows us to access contentBlockingEvent in the parent process
through WindowGlobalParent object.

ContentBlockingEvent in RemoteSecurityUI is updated after receiving notification from the child process.
Since contentBlockingEvent will be removed from the child process, this patch removes the use of
contentBlockingEvent in RemoteSecurityUI and uses the API defined in WindowGlobalParent.

Depends on D55621

We should be able to acess contentBlockingEvent directly via
WindowGlobalParent::ContentBlockingEvent.
Update and store contentBlockingEvent in RemoteSecurityUI is no longer needed.

Depends on D55622

Attachment #9113147 - Attachment description: Bug 1600878 - P2. Use contentBlockingEvent in the WindowGlobalParent instead of contentBlockingEvent in RemoteSecurityUI r=timhuang → Bug 1600878 - P2. Use contentBlockingEvents in the WindowGlobalParent instead of contentBlockingEvent in RemoteSecurityUI r=timhuang
Attachment #9113147 - Attachment description: Bug 1600878 - P2. Use contentBlockingEvents in the WindowGlobalParent instead of contentBlockingEvent in RemoteSecurityUI r=timhuang → Bug 1600878 - P2. Use contentBlockingEvents in WindowGlobalParent instead of contentBlockingEvent in RemoteSecurityUI r=timhuang
Pushed by dlee@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7535e00d33e9 P1. Add contentBlockingEvent attribute to WindowGlobalActors.webidl r=timhuang,Ehsan https://hg.mozilla.org/integration/autoland/rev/bd432376ef0d P2. Use contentBlockingEvents in WindowGlobalParent instead of contentBlockingEvent in RemoteSecurityUI r=timhuang,Ehsan https://hg.mozilla.org/integration/autoland/rev/89dcc457c42f P3. Do not store contentBlockingEvent in RemoteSecurityUI.jsm r=timhuang,Ehsan
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: