Content Security Policy: Couldn’t process unknown directive ‘plugin-types’ causing TIMEOUT for all tests in content-security-policy/plugin-types/
Categories
(Core :: DOM: Security, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox77 | --- | fixed |
People
(Reporter: jmaher, Assigned: jmaher)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
we have 7 tests in this web-platform-tests directory: content-security-policy/plugin-types/. All but 1 test (this test doesn't say plugin-type, it tries shockwave-flash) set content:
<meta http-equiv="Content-Security-Policy" content="plugin-types application/pdf;">
or something similar with plugin-types as the main word. All of these tests timeout and are never expected to pass.
Either we do not support plugin-types, or these tests are not written properly for firefox.
|
Assignee | |
Comment 1•4 years ago
|
||
:ckerschb, can you help me figure out if these tests are supposed to run and if we support 'plugin-types'? Maybe you know someone to redirect this question to.
|
||
Comment 2•4 years ago
|
||
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #1)
:ckerschb, can you help me figure out if these tests are supposed to run and if we support 'plugin-types'? Maybe you know someone to redirect this question to.
As of today, Firefox does not support the CSP directive plugin-types and it's currently also not on our roadmap to support that directive. I guess we can disable those tests for now.
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 3•4 years ago
|
||
disable content-security-policy/plugin-types/ tests as we do not support them
|
||
Comment 4•4 years ago
|
||
Does "not on our roadmap" in this case mean "we never expect to support this property" (e.g. because we don't support plugins and don't plan to change that)?
|
|
||
Comment 5•4 years ago
|
||
(In reply to James Graham [:jgraham] from comment #4)
Does "not on our roadmap" in this case mean "we never expect to support this property" (e.g. because we don't support plugins and don't plan to change that)?
Never say never, but at least for the foreseen future we are not going to support plugin-types.
|
|
||
Updated•4 years ago
|
Pushed by jmaher@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/477980afd0f7 disable content-security-policy/plugin-types/ tests as we do not support them. r=ckerschb
|
||
Comment 7•4 years ago
|
||
| bugherder | ||
Description
•