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
Describe the bug
When set to "disabled", the underlying input field does not get the "disabled" attribute, so it's still editable. You cannot click on it since the wrapping span has pointer-events: none, but if you set a label for this input, you still can edit a disabled field, which is kinda no-go in terms of security.
Good thing: Updates to the disabled field do not fire an update event, which might be good or bad, depending on whether we consider security or UX.
Describe the bug
When set to "disabled", the underlying input field does not get the "disabled" attribute, so it's still editable. You cannot click on it since the wrapping span has pointer-events: none, but if you set a label for this input, you still can edit a disabled field, which is kinda no-go in terms of security.
Good thing: Updates to the disabled field do not fire an update event, which might be good or bad, depending on whether we consider security or UX.
To Reproduce
Expected behavior
The input inside the Input component should have a disabled attribute.
The text was updated successfully, but these errors were encountered: