-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
Accessibility: on systems with larger DPI scaler (e.g. tablet-like form factor or user with poor sight) start screen might be cut off #4063
Comments
What's your window/screen resolution in pixels? |
800x1280 with DPI scaler 1.75 |
I believe HTML/CSS-wise we're good. It appears like the window itself goes beyond the screen bounds in the original post. msrdc_qr4PfK2HtU.mp4On Windows I cannot resize the window to shorter than 400px. I think we set the
Shall we just lower it? Do we have a reason to have it no lower than 450? |
Maybe we can lower even further or even remove the min- screen size. (but then people shouldn't complain if the interface is not working on 100x100px for example...)
That was the minimum-somewhat-usable size before the introduction of small screen mode. |
DEFAULT_WIDTH in Dialog.tsx is set to 500. I did drag it over into a #4006. I'm not sure that might cause problems and I can't check right now, just saying. |
It seems like on systems with a larger DPI scaler given a relatively normal or smaller screen size, e.g. tablet-like form factor where people may often still run Desktop Linux, or on computers of user with poor sight, the delta chat start screen seems to be cut off. It would be nice if it was more responsive and scrollable to work around that.
Operating System (Linux/Mac/Windows/iOS/Android): postmarketOS Edge x64 desktop (Alpine Linux based), using a regular KDE Desktop and not any kind of mobile desktop
Delta Chat Version: v1.140.2 (latest on flathub)
Expected behavior: start screen and about screen aren't cut off
Actual behavior: it's cut off:
The about screen can't fully scroll to the buttom either:
Steps to reproduce the problem:
Screenshots: see above
Logs:
The text was updated successfully, but these errors were encountered: