Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Blazor] Fix antiforgery not being available after first render #57237

Merged
merged 5 commits into from
Aug 9, 2024

Conversation

javiercn
Copy link
Member

@javiercn javiercn commented Aug 8, 2024

Fixes #54533

@javiercn javiercn requested a review from a team as a code owner August 8, 2024 18:19
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-blazor Includes: Blazor, Razor Components label Aug 8, 2024
javiercn and others added 2 commits August 8, 2024 20:44
…Host.cs

Co-authored-by: Mackinnon Buck <mackinnon.buck@gmail.com>
Copy link
Member

@halter73 halter73 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fact that even we run into these kinds of bugs when trying to use PersistentComponentState from our AntiforgeryToken component, makes me think we should raise the priority of #51584.

@javiercn javiercn enabled auto-merge (squash) August 9, 2024 10:55
@javiercn javiercn merged commit 9e015b7 into main Aug 9, 2024
26 checks passed
@javiercn javiercn deleted the javiercn/antiforgery-interactive branch August 9, 2024 13:21
@dotnet-policy-service dotnet-policy-service bot added this to the 9.0-rc1 milestone Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Antiforgery state doesn't always reach interactive components
3 participants