[11.0 P1] Update CSP guidance for inline JS removal #36686
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
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Content Security Policy (CSP) guidance for Blazor to reflect the removal of inline JavaScript in the NavMenu component starting with .NET 11.0. The change eliminates the need for the unsafe-hashes directive and specific hash values that were previously required for the navigation toggler functionality.
Changes:
- Updated generic guidance text for client-side Blazor apps to remove the specific NavMenu example while keeping general unsafe-hashes guidance
- Added new CSP policy example for .NET 11.0+ that excludes the unsafe-hashes directive and hash value
- Adjusted moniker ranges to properly version the CSP examples between .NET 8.0-10.0 and .NET 11.0+
tdykstra
approved these changes
Jan 26, 2026
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.
Fixes #36684
Addresses #36448
Wade or Tom ... Just knocking out the hash guidance now that the inline JS will be going away at 11.0.
I agreed (for the most part) with one of Copilot's suggestions and made a change to address it. I didn't agree with the other suggestion.
Internal previews