[Warning Fix] Addition of single quote around unsafe_inline to avoid it being considered as url. #242
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I encountered this warning on Mozilla Firefox. The console warning is just spammed with the same message (Magento 2.4.5).
Here the message on a french browser :
Content Security Policy: https://unsafe-inline/ a été interprété comme un nom d’hôte et non comme un mot-clé. S’il s’agissait vraiment d’un mot-clé, utilisez 'unsafe-inline' (entouré d’apostrophes)
Basically, it reports that unsafe-inline without single quote is considered as host name.
Adding those single quotes remove the message in the console.
Regards,