-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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 WASM: Button-tag is not correctly disabled within a disabled fieldset #34749
Comments
Addition: According to the W3C site it should not be possible. Here's a simple online example from me: https://www.w3schools.com/code/tryit.asp?filename=GSUO92QUUK60 |
Thanks for contacting us. This indeed seems to be the expected behavior: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fieldset#attr-disabled. |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
Looks like a browser bug to me. Enabling Blazor example: https://blazorfiddle.com/s/szj9ja01 The current attempt to disable events like aspnetcore/src/Components/Web.JS/src/Rendering/Events/EventDelegator.ts Lines 336 to 342 in dd476b1
Other frameworks like react have the same issue: facebook/react#7711 |
Describe the bug
When placing a
<button>
within a<fieldset disabled>
and the button contains anything other than plain text it's click handler ist executed eventhough it shouldn't be.To Reproduce
The following code contains an enabled state and 3 disabled states where the first disabled state is really disabled and the last two are showing the non expected behavior.
Further technical details
5.0.302
dotnet --info
VS 2019 Community, 16.10.4
The text was updated successfully, but these errors were encountered: