-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Closed
Labels
Priority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withoutarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor ComponentsblockedThe work on this issue is blocked due to some dependencyThe work on this issue is blocked due to some dependencyenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing onefeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyThis issue is related to and / or impacts Blazor WebAssemblytask
Milestone
Description
Runtime made the necessary changes that unsafe-eval
may no longer be required for Blazor WASM: dotnet/runtime#59416
Note, there's also a Chrome bug which may come into play here (WebAssembly/content-security-policy#7)
This issue tracks validating this fix, and the associated documentation updates.
Original CSP Issue: #34428
nic547, veikkoeeva, davidchavezgrant, boukenka, thomas-kua and 5 more
Metadata
Metadata
Assignees
Labels
Priority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withoutarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor ComponentsblockedThe work on this issue is blocked due to some dependencyThe work on this issue is blocked due to some dependencyenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing onefeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyThis issue is related to and / or impacts Blazor WebAssemblytask