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
Web admin settings page number input broken #9361
Comments
Oh also, this is the code handling the number input and the setting of the minimum/maximum value: |
NicholasFlamy
changed the title
Web admin settings page number input broken on mobile
Web admin settings page number input broken
May 9, 2024
Big edit: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The bug
The number input field value is changed to the minimum when going under the minimum value and changed to the maximum when going over the maximum value. This is intended. The problem with this is that if you try and backspace the value to type in a new one, it'll become 0 and instantly update to the minimum.
What should happen is it waits until you tap outside of the input box (deselecting/defocusing the box) so that you're able to set the value.
Note: Ignore the fact I'm in an unreleased part of the settings, this applies to the other settings with number inputs, including job concurrency, Image Quality, ML Settings, etc.
This screenshot is where I hit backspace on the value and it instantly resets to the minimum:
This is the only workaround, putting your cursor in front or behind the value and typing some digits to make it your value with the old value now added to yours and you can backspace what was the old value:
The OS that Immich Server is running on
N/A
Version of Immich Server
All
Version of Immich Mobile App
N/A
Platform with the issue
Your docker-compose.yml content
N/A
Your .env content
Reproduction steps
Relevant log output
No response
Additional information
I'm using a Samsung Galaxy S21 on Android 14 with Google Chrome. Also tested on Brave on Linux Mint.
The text was updated successfully, but these errors were encountered: