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

MudChip OnClick handler broke in 5.1.5: NullReferenceException is thrown when OnClick is set #2911

Closed
1 of 2 tasks
mikequ-taggysoft opened this issue Oct 1, 2021 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@mikequ-taggysoft
Copy link

mikequ-taggysoft commented Oct 1, 2021

Bug type

Component

Component name

MudChip

What happened?

This was working fine as of 5.1.4, but 5.1.5 broke it: whenever OnClick is set in MudChip, the exception would be thrown.

See TryMudBlazor.

Expected behavior

Should work.

Reproduction link

https://try.mudblazor.com/snippet/cYGPlkOFPzuDhyUv

Reproduction steps

  1. Add an OnClick handler to MudChip.
  2. Run.
    ...

Relevant log output

blazor.server.js:21 [2021-10-01T04:09:45.960Z] Error: System.NullReferenceException: Object reference not set to an instance of an object.
at MudBlazor.MudChip.get_Classname()
at MudBlazor.MudChip.BuildRenderTree(RenderTreeBuilder __builder)
at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()

Version (bug)

5.1.5

Version (working)

5.1.4

What browsers are you seeing the problem on?

Chrome

On what operating system are you experiencing the issue?

Windows

Pull Request

  • I would like to do a Pull Request

Code of Conduct

  • I agree to follow this project's Code of Conduct
@JonBunator
Copy link
Member

Duplicate of #2866

@JonBunator JonBunator added duplicate This issue or pull request already exists and removed triage labels Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants