Content Security Policy: Couldn’t process unknown directive ‘script-src-elem’ causing all tests to timeout or fail in content-security-policy/script-src-attr-elem/ directory
Categories
(Core :: DOM: Security, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox77 | --- | fixed |
People
(Reporter: jmaher, Assigned: jmaher)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
there are 8 tests in the content-security-policy/script-src-attr-elem/ directory, all of them are unconditionally marked as expected timeout or fail and I can confirm that running locally. I see this in the console:
Content Security Policy: Couldn’t process unknown directive ‘script-src-elem’
I suspect this is related to bug 1632083 where the directive is 'plugin-types'.
this is slowing down test execution and wasting time.
|
Assignee | |
Comment 1•4 years ago
|
||
:ckerschb, do we support 'script-src-elem'? If so, can we fix these tests?
|
|
Assignee | |
Comment 2•4 years ago
|
||
this is also the case for the 6 'style-src-attr' tests:
https://searchfox.org/mozilla-central/source/testing/web-platform/tests/content-security-policy/style-src-attr-elem
|
||
Comment 3•4 years ago
|
||
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #2)
this is also the case for the 6 'style-src-attr' tests:
https://searchfox.org/mozilla-central/source/testing/web-platform/tests/content-security-policy/style-src-attr-elem
Joel, I guess we can disable both, because Firefox does not support script-src-elem and also not style-src-attr and it's not on our roadmap to support those directives anytime soon.
|
|
Assignee | |
Comment 4•4 years ago
|
||
a followup question- there are other tests that reference script-src-elem and style-src-attr which are in different directories, for example:
https://searchfox.org/mozilla-central/search?q=script-src-elem&path=
If the test is only ever marked as failed or timeout should I include those in a patch to mark as not-implemented (which will be the same as disabled)
|
|
||
Comment 5•4 years ago
|
||
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #4)
a followup question- there are other tests that reference script-src-elem and style-src-attr which are in different directories, for example:
https://searchfox.org/mozilla-central/search?q=script-src-elem&path=If the test is only ever marked as failed or timeout should I include those in a patch to mark as not-implemented (which will be the same as disabled)
Yes, I think that would be great - thank you!
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 6•4 years ago
|
||
...they include script-srcelem exception.
These are as backlog assuming Mozilla has plans to implement these features in the future.
Move wpt tests for src-src-attr-elem and style-src-attr-elem to run as backlog tsts (tier2).
|
|
||
Updated•4 years ago
|
|
||
Updated•4 years ago
|
Pushed by jmaher@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a0fbb0c39d77 move wpt tests for script-src-attr-elem and style-src-attr-elem to run as backlog. r=ckerschb tests here are also marked as backlog as they are unconditionally marked as fail/timeout for all their tests (typically 1 test) and...
|
||
Comment 8•4 years ago
|
||
| bugherder | ||
Description
•