Closed Bug 1698767 Opened 2 months ago Closed 2 months ago

Investigate internal content policy type in SecFetch::IsUserTriggeredForSecFetchSite

Categories

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

task

Tracking

()

RESOLVED FIXED
88 Branch
Tracking Status
firefox88 --- fixed

People

(Reporter: ngogge, Assigned: ngogge)

References

(Blocks 1 open bug)

Details

(Whiteboard: [domsecurity-active])

Attachments

(1 file)

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
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
You need to log in before you can comment on or make changes to this bug.