1639851 - Different warning messages displayed in Web Console with "fission.autostart" pref set to true or false

Status: NEW

(DevTools :: Console, defect)

Description

[Camelia Badau [:cbadau], Release Desktop QA]

Attachment: issue.png

Affected versions

• Nightly 78.0a1 (2020-05-20)

Affected platforms

• Windows 10 x64
• Ubuntu 18.04 x64
• macOS 10.15

Steps to reproduce

1. Launch Firefox and set "fission.autostart" pref to true in about:config. Restart Firefox.
2. Open a New private browsing window.
3. Go to https://senglehardt.com/test/trackingprotection/test_pages/tracking_protection.html .
4. Open Web Console (Menu -> Tools -> Web Developer).

Expected result

• Two warning messages with the following form should be displayed:
  • The resource at “<URL>” was blocked because content blocking is enabled.
  • Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled.

Actual result

• Only one warning message is displayed when the "fission.autostart" pref is set to true:
  • The resource at “<URL>” was blocked because content blocking is enabled.

Regression range

• Will check if one ASAP.

Additional notes

• See attachment "issue.png".
• When the "fission.autostart" pref is set to false, both warning messages are displayed in the Web Console:
  • The resource at “<URL>” was blocked because content blocking is enabled.
  • Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled.

Comment 1

[Chris Peterson [:cpeterson]]

Steven, does this look like a bug in content blocking or in the DevTools console logging?

The tracker blocking test in screenshot in comment 0 appear to have passed, suggesting a DevTools console bug.

Comment 2

[Dimi Lee [:dimi][:dlee]]

I'll check this issue.

Comment 3

[Dimi Lee [:dimi][:dlee]]

The problem is that the tracker frame and the devtool's console service are not in the same process, so console service can't receive the message.
Chris, do you know whether this is a known issue? or there is a fission-compatible console API we can use?

Note. the API anti-tracking is using to report console is nsContentUtils::ReportToConsoleByWindowID.

Comment 4

[Chris Peterson [:cpeterson]]

(In reply to Dimi Lee [:dimi][:dlee] from comment #3)

The problem is that the tracker frame and the devtool's console service are not in the same process, so console service can't receive the message.
Chris, do you know whether this is a known issue? or there is a fission-compatible console API we can use?

Note. the API anti-tracking is using to report console is nsContentUtils::ReportToConsoleByWindowID.

Alex, what Fission-compatible API should C++ code use to log messages to the web console? Is "Support logging early messages during target-switching and remoted iframes load" bug 1614291 related?

I don't see any obviously-related bugs when looking at the dependency tree for the "Make Console Fission-ready" meta bug 1561943.

Comment 5

[Alexandre Poirot [:ochameau]]

Yes this is probably one of the many feature that will only work once we get to fix bug 1614291.
I'm not flagging as duplicate in order to verify that this one usecase works once we fixed the console.

Comment 6

[Chris Peterson [:cpeterson]]

Adding dt-fission whiteboard tag to DevTools bugs that mention Fission or block Fission meta bugs but don't already have a dt-fission whiteboard tag.

Comment 7

[Chris Peterson [:cpeterson]]

Moving dt-fission bugs to Fission MVP.

Comment 8

[Neha Kochar [:neha]]

Bulk change of all bugs with whiteboard tag of dt-fission to Fission MVP milestone.

Comment 9

[Chris Peterson [:cpeterson]]

Moving old "dt-fission" bugs to "dt-fission-future" because they don't block Fission MVP.