Right now, the ContentBlockingLog is located on the document of the top-level window. This is incompatible to the Fission since the top-level window might not be accessible if it is cross-origin. In order to make this work in the Fission. We'll remove ContentBlockingLog from child process and store it in the parent process instead.
Bug 1599046 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Right now, the ContentBlockingLog is located on the document of the top-level window. This is incompatible to the Fission since the top-level window might not be accessible if it is cross-origin. In order to make this work in the Fission. We'll remove ContentBlockingLog from the child process and store it in the parent process instead.