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

The disabled Native Input is not really disabled #389

Closed
PekoPPT opened this issue Apr 10, 2023 · 0 comments
Closed

The disabled Native Input is not really disabled #389

PekoPPT opened this issue Apr 10, 2023 · 0 comments
Assignees
Labels
Bug Item which indicates that something is not working FP: Completed SEV: High

Comments

@PekoPPT
Copy link
Contributor

PekoPPT commented Apr 10, 2023

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

  1. Open this CodeSandbox

Expected behavior
The input inside the Input component should have a disabled attribute.

@PekoPPT PekoPPT added Bug Item which indicates that something is not working SEV: High labels Apr 10, 2023
@PekoPPT PekoPPT added this to the R2 2023 - Increment 2 (12.04.2023) milestone Apr 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Item which indicates that something is not working FP: Completed SEV: High
Projects
None yet
Development

No branches or pull requests

2 participants