Repository navigation
fix(formplayer): Improved number input UX - #667
Merged
Merged
Conversation
najuna-brian
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Title
This PR aims to improve the UX when inputting numbers in input fields. Previously the OS native number input field would clamp values to be within any defined min- and max-values, causing the frustrating effect of having the input changing while entering it, making it impossible to write certain numbers despite them being valid (e.g. typing "22" in a field with min-value = 4, would require entering "2" and then "2", but the input clamper would change the first "2" to a "4", thus making it impossible to write 22).
This PR relaxes that behaviour and simply shows a warning message for invalid values.