You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting the Indeterminate property of the NimbleCheckbox in Blazor to true does not work. The checkbox does not changes to an indeterminate state.
💻 Repro or Code Sample
Adding this code to a Blazor file does not set the checkbox to an indeterminate state <NimbleCheckbox Indeterminate="true"></NimbleCheckbox>
🤔 Expected Behavior
The checkbox should be in an indeterminate state
😯 Current Behavior
The checkbox is unchecked.
💁 Possible Solution
There is no workaround since indeterminate is a property and not an attribute. Blazor does not support setting properties.
🔦 Context
Found the issue while debugging another issue. I am not using a checkbox right now, but this bug needs to be fixed since other issues might be running into this and I might eventually have a need for a checkbox.
🌍 Your Environment
OS: Windows 11
Browser: Chrome
Version: 19.5.1
The text was updated successfully, but these errors were encountered:
🐛 Bug Report
Setting the Indeterminate property of the NimbleCheckbox in Blazor to true does not work. The checkbox does not changes to an indeterminate state.
💻 Repro or Code Sample
Adding this code to a Blazor file does not set the checkbox to an indeterminate state
<NimbleCheckbox Indeterminate="true"></NimbleCheckbox>
🤔 Expected Behavior
The checkbox should be in an indeterminate state
😯 Current Behavior
The checkbox is unchecked.
💁 Possible Solution
There is no workaround since
indeterminate
is a property and not an attribute. Blazor does not support setting properties.🔦 Context
Found the issue while debugging another issue. I am not using a checkbox right now, but this bug needs to be fixed since other issues might be running into this and I might eventually have a need for a checkbox.
🌍 Your Environment
OS: Windows 11
Browser: Chrome
Version: 19.5.1
The text was updated successfully, but these errors were encountered: