Unable to save settings when numerical values are input while Japanese keyboard is open. 2 works, but "２" doesn't. 二 also doesn't work (not as big of an issue IMO). This issue probably exists in a lot of places. May be worth trying to coerce numerical values in numerical inputs.
This is an interesting issue. There's a few conflicting things - maybe there's a solution I'm missing.
1. On the client side, the input boxes are set to type="number", so it's rejecting any of the "J numbers" before it can even get saved into the box for submission. It doesn't *look* like I can intercept that, especially with the Japanese IME hijacking the input for auto-completion.
2. The backend that validates numbers already does the ０ to 0 style conversion, has for years (at least, anywhere where I'm validating on a number, and not a more general string)
So I could remove type="number", but that would remove the best part of that with regards to mobile devices, which is popping up the numeric pad instead of the keyboard.
I'm actually kinda curious as to how you got the ３ in there - must be a browser-dependent thing, because Chrome rejects it outright - it is there in the Japanese IME, then vanishes as soon as you hit enter to "confirm" the IME selection.
Safari lets me input it, but the input.value shows it is "". I confirmed Chrome won't let you put anything there, nor will Chrome on Android, even when pasting.
I guess I can just deal with it And fix it when it happens
And fix it when it happens