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
Describe the bug
Since the update to Nextcloud 29, pressing Ctrl+Backspace in an unordered list behaves weirdly. When pressing it with more than one word left in the current line/item, it behaves normally and deletes the word before the cursor. However, when pressing it with only one word left in the current line, it inserts a new item below and focusses this item. However, it only happens with Firefox, not with Chromium; there, it behaves normally.
Have a look at the following video to get a better understanding:
Schermopname.van.2024-05-27.17-51-16.mp4
In the video, I only press Ctrl+Backspace, nothing else.
To Reproduce
Steps to reproduce the behavior:
Have an unordered list
Press Ctrl+Backspace with only one item left in the line
Expected behavior
The last remaining word is deleted as well.
Screenshots
See video above.
Server details:
Nextcloud version: 29.0.1
PHP Version: 8.3
Database: mariadb Ver 15.1 Distrib 10.5.23-MariaDB, for Linux (x86_64) using EditLine wrapper
Describe the bug
Since the update to Nextcloud 29, pressing Ctrl+Backspace in an unordered list behaves weirdly. When pressing it with more than one word left in the current line/item, it behaves normally and deletes the word before the cursor. However, when pressing it with only one word left in the current line, it inserts a new item below and focusses this item. However, it only happens with Firefox, not with Chromium; there, it behaves normally.
Have a look at the following video to get a better understanding:
Schermopname.van.2024-05-27.17-51-16.mp4
In the video, I only press Ctrl+Backspace, nothing else.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The last remaining word is deleted as well.
Screenshots
See video above.
Server details:
Client details:
Logs
Nextcloud log (data/nextcloud.log)
Probably not necessary; if it is, just tell me.
Browser log
console-export-2024-5-27_18-3-41.txt
The text was updated successfully, but these errors were encountered: