Repository navigation
fix: pass the page's CSP nonce to the MUI style cache (1.0.1) - #19
Merged
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
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.
MUI injects its styles through Emotion as runtime style tags, which a strict style-src CSP blocks, so Strata's deployed UI rendered unstyled. UiProvider now builds its own layered Emotion cache that reads the nonce from a meta csp-nonce tag. It keeps MUI's @layer mui wrapping, declares the layer order in a nonce'd style tag at the top of head, and adds @emotion/cache as a peer dependency (already in every app through @emotion/react). Without the meta tag nothing changes.
Checked against Strata's server-served build with a nonce CSP: no CSP violations, layer order theme, base, mui, components, utilities.