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
The problem is that something like 123. gets parsed as the number 123, which, when formatted, is just 123. Since bind:valueAsNumber is a "controlled" input, typing the . will automatically get removed by the signal updating. This results in the bug where we can never type 123.456 since we'll never get pass the .
Setting
bind:value
orbind:valueAsNumber
for an input of typenumber
restricts what you can type in it. As far as I can tell:.
does nothing in Firefox, and moves the cursor to the beginning of the field in ChromiumTo Reproduce
A maintainer has provided an executable that reproduces the problem. Maybe they could add the source code to this issue report.
Expected behavior
Setting
bind:value
orbind:valueAsNumber
does not affect how a number input responds to typing.Environment
The text was updated successfully, but these errors were encountered: