Closed
Bug 1639538
Opened 5 years ago
Closed 5 years ago
/content-security-policy/reporting-api/reporting-api-sends-reports-on-violation.https.sub.html is expected timeout
Categories
(Core :: DOM: Security, defect, P2)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
mozilla78
| Tracking | Status | |
|---|---|---|
| firefox78 | --- | fixed |
People
(Reporter: jmaher, Assigned: jmaher)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
I see that /content-security-policy/reporting-api/reporting-api-sends-reports-on-violation.https.sub.html is failing in automation and I can reproduce it locally.
I see this in the console locally:
Content Security Policy: Couldn’t process unknown directive ‘report-to’
I assume this is something we do not support, but there are dozens of instances of 'report-to' in other tests:
https://searchfox.org/mozilla-central/search?q=report-to&path=&case=false®exp=false
:ckerschb, can you take a look at this bug?
Flags: needinfo?(ckerschb)
|
||
Comment 1•5 years ago
|
||
We do not support report-to - backlog seems fine to me - thanks!
Flags: needinfo?(ckerschb)
|
Assignee | |
Comment 2•5 years ago
|
||
move reports-to tests to backlog (tier-2)
|
||
Updated•5 years ago
|
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
|
|
||
Updated•5 years ago
|
Severity: -- → S3
Priority: -- → P2
Whiteboard: [domsecurity-active]
Pushed by jmaher@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a4c8a707e47b
move reports-to tests to backlog (tier-2). r=ckerschb
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox78:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in
before you can comment on or make changes to this bug.
Description
•