Skip to content

Remove "'none'" value for merged directives with multiple declarations#6

Merged
frux merged 1 commit intofrux:masterfrom
milo526:master
Nov 14, 2024
Merged

Remove "'none'" value for merged directives with multiple declarations#6
frux merged 1 commit intofrux:masterfrom
milo526:master

Conversation

@milo526
Copy link
Copy Markdown
Contributor

@milo526 milo526 commented Oct 7, 2023

The "'none'" value is used to indicate that no resources are allowed. If the "'none'" value is used in combination with other resources, it should be ignored as defined by https://w3c.github.io/webappsec-csp/#match-url-to-source-list Some browsers however, warn on this behaviour. It is therefor best to remove the "'none'" value in this instance.

Fixes #5

The "'none'" value is used to indicate that no resources are allowed.
If the "'none'" value is used in combination with other resources, it should be ignored as defined by https://w3c.github.io/webappsec-csp/#match-url-to-source-list
Some browsers however, warn on this behaviour. It is therefor best to remove the "'none'" value in this instance.

Fixes frux#5
@frux frux merged commit 352d6e7 into frux:master Nov 14, 2024
@frux
Copy link
Copy Markdown
Owner

frux commented Nov 14, 2024

@milo526 Thank you! Just published in version 6.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Combining 'none' and other source expressions errors in Chrome

2 participants