Closed Bug 1659416 Opened 10 months ago Closed 9 months ago

Partitioned cookie or storage access message is triggered twice in WebConsole

Categories

(DevTools :: Console, defect)

Firefox 81
defect

Tracking

(firefox81 affected)

RESOLVED INVALID
Tracking Status
firefox81 --- affected

People

(Reporter: cbadau, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached image issue.png

Affected versions

  • Nightly 81.0a1 (2020-08-16)

Affected platforms

  • Windows 10
  • Ubuntu 18.04
  • macOS 10.15

Steps to reproduce

  1. Launch Firefox.
  2. Set network.cookie.cookieBehavior = 5, privacy.partition.network_state= true and urlclassifier.trackingAnnotationTable.testEntries = known-tracker.englehardt-tracker.com. Restart the browser.
  3. Navigate to https://senglehardt.com/test/dfpi/simple.html.
  4. Open the Web Console.
  5. Observe the log console displayed for the storage access blocked.
    => "Partitioned cookie or storage access was provided to “<URL>” because it is loaded in the third-party context and storage partitioning is enabled." message is displayed.
  6. Click on the "Show hide/message details." icon (the triangle pointing right).

Expected result

Actual result

  • The message is displayed twice in the Web Console.

Regression range

  • It is not a regression (the issue is also reproducible on Nightly 80.0a1).

Additional notes

  • See attachment "issue.png".

Suggested severity

  • S4
Has STR: --- → yes

This is expected because the test page accesses multiple APIs (or accesses the same API multiple times). We'll print a message for each assess. I made a similar test page that only checks cookies, and you'll see two warning messages on the first visit (since it will both read document.cookie and then write document.cookie) and only one message on the second visit (since it only reads document.cookie when the result is non-empty). See: https://senglehardt.com/test/dfpi/simple_only_cookies.html.

Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.