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 pop-up when editing an entry adapts to the screen size of the smartphone.
This was always the case up to version 0.8.0
Actual behavior
Since Tables 0.8.1, the pop-up for editing a table entry is no longer properly adapted to the mobile website.
This does not occur with every table. However, I cannot explain why.
It is also no longer possible to close the pop-up, as the cross at the top right can no longer be reached to close it.
Scrolling is not possible. You can only hope to reach the X in landscape format. But even here not all fields are visible. The save button does not appear either.
Tables app version
0.8.1
Browser
Brave, Chrome
Client operating system
Android 14
Operating system
Debian
Web server
Nginx
PHP engine version
PHP 8.2
Database
MariaDB
Additional info
No response
The text was updated successfully, but these errors were encountered:
Hm, this might be an effect of an update of a lib, nextcloud/vue perhaps, or one of those. As we did not have a related UI change between 0.8.0 and 0.8.1.
Steps to reproduce
Expected behavior
The pop-up when editing an entry adapts to the screen size of the smartphone.
This was always the case up to version 0.8.0
Actual behavior
Since Tables 0.8.1, the pop-up for editing a table entry is no longer properly adapted to the mobile website.
This does not occur with every table. However, I cannot explain why.
It is also no longer possible to close the pop-up, as the cross at the top right can no longer be reached to close it.
Scrolling is not possible. You can only hope to reach the X in landscape format. But even here not all fields are visible. The save button does not appear either.
Tables app version
0.8.1
Browser
Brave, Chrome
Client operating system
Android 14
Operating system
Debian
Web server
Nginx
PHP engine version
PHP 8.2
Database
MariaDB
Additional info
No response
The text was updated successfully, but these errors were encountered: