fix: CSP error in debugbar #1242
Merged
Conversation
This file contains hidden or 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
Resolve an error when CSP is enabled, the style attribute in the table cause an error in console.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Resolve an error when CSP is enabled and use debugbar in development environment, the style attribute in the table (from the collector) cause an error in browser console, changing the style attribute to a width attribute fix the issue.
index.php?debugbar:46 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' 'nonce-98f45b1a6e3d510a2fe4474e'". Either the 'unsafe-inline' keyword, a hash ('sha256-AjG9eor6SyhAUzJE5wyV4y7++Gv+bkiPYFnboahgMlA='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.