Closed Bug 1698767 Opened 3 years ago Closed 3 years ago

Investigate internal content policy type in SecFetch::IsUserTriggeredForSecFetchSite

Categories

(Core :: DOM: Security, task, P2)

Product:
Core
Component:
DOM: Security
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
88 Branch
Tracking Flags:
Tracking Status
firefox88 --- fixed

People

(Reporter: n.goeggi, Assigned: n.goeggi)

References

Details

(Whiteboard: [domsecurity-active])

Attachments

(1 file)

Bug 1698767 - Use ExtContentPolicyType instead of InternalContentPolicyType in SecFetch::IsUserTriggeredForSecFetchSite
48 bytes, text/x-phabricator-request
Details | Review

Why are we using the internal content policy type here instead of the external content policy type like here?

Assignee: nobody → ngogge
Blocks: 1695911
Severity: -- → S3
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [domsecurity-active]
Pushed by mozilla@christophkerschbaumer.com:
https://hg.mozilla.org/integration/autoland/rev/4ab214750288
Use ExtContentPolicyType instead of InternalContentPolicyType in SecFetch::IsUserTriggeredForSecFetchSite r=ckerschb

https://hg.mozilla.org/mozilla-central/rev/4ab214750288

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox88: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: