Losing focus while editing Title field on new or existing card

[estux]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Describe the bug
If I start editing the title on new or existing card and I move the mouse cursor out of the card border, the title field looses focus. While I continue typing I can accidentally activate other keyboard commands or edit the title of another card where the mouse cursor is over.

To Reproduce
Steps to reproduce the behavior:

1. Go to a Deck board
2. Click on + in a List to add a new card.
3. Move mouse cursor over another card
4. Cannot type in title field anymore

or

1. and 2. as before
2. Start typing the title in the field
3. Move mouse cursor (by mistake, as you have physical mouse that get in the way near the keyboard)
4. You moved over another card title field and you're editing its title

or

1. and 2. as before
2. Start typing the title in the field
3. Move mouse cursor (by mistake) in an empty area of the board (you stopped editing the title field)
4. As you're still typing you could activate random keyboard commands associated to archive card, assign, create a new card and so on, creating a mess!

or

1. and 2. as before
2. Click on a title of an already existing card in the board, to edit it.
3. Start typing
4. Move your mouse cursor (by mistake) out of the card border
5. As you're still typing you risk again creating a mess activating random keyboard commands

Expected behavior
The title field should not loose focus if I'm still editing it. The title field should not loose focus until I save/confirm what I typed.

Screenshots
Sadly screenshots don't help to explain the problem this time.

Client details:

• OS: Windows 10
• Browser: Firefox
• Version 122.0.1
• Device: laptop

Server details

Operating system: Linux 5.15.136-1-pve

Web server: nginx/1.18.0 (fpm-fcgi)

Database: mysql 10.5.23

PHP version: 8.2.14

Nextcloud version: 28.0.3 - 28.0.3.2

Where did you install Nextcloud from: unknown (as I'm paying a provider for the service)

Signing status:
No errors have been found.

List of activated apps:

Enabled:

• activity: 2.20.0
• bookmarks: 13.1.3
• bruteforcesettings: 2.8.0
• calendar: 4.6.6
• camerarawpreviews: 0.8.4
• circles: 28.0.0-dev
• cloud_federation_api: 1.11.0
• collectives: 2.10.0
• comments: 1.18.0
• contacts: 5.5.3
• contactsinteraction: 1.9.0
• cospend: 1.6.1
• dashboard: 7.8.0
• dav: 1.29.1
• deck: 1.12.2
• federatedfilesharing: 1.18.0
• federation: 1.18.0
• files: 2.0.0
• files_pdfviewer: 2.9.0
• files_reminders: 1.1.0
• files_sharing: 1.20.0
• files_trashbin: 1.18.0
• files_versions: 1.21.0
• firstrunwizard: 2.17.0
• forms: 4.1.1
• groupfolders: 16.0.4
• inventory: 0.1.2
• logreader: 2.13.0
• lookup_server_connector: 1.16.0
• maps: 1.3.1
• news: 25.0.0-alpha3
• nextcloud_announcements: 1.17.0
• notes: 4.9.2
• notifications: 2.16.0
• oauth2: 1.16.3
• password_policy: 1.18.0
• photos: 2.4.0
• polls: 6.1.6
• privacy: 1.12.0
• provisioning_api: 1.18.0
• recommendations: 2.0.0
• related_resources: 1.3.0
• richdocuments: 8.3.2
• serverinfo: 1.18.0
• settings: 1.10.1
• sharebymail: 1.18.0
• spreed: 18.0.5
• support: 1.11.0
• survey_client: 1.16.0
• suspicious_login: 6.0.0
• systemtags: 1.18.0
• tables: 0.6.6
• tasks: 0.15.0
• text: 3.9.1
• theming: 2.3.0
• twofactor_backupcodes: 1.17.0
• updatenotification: 1.18.0
• user_status: 1.8.1
• viewer: 2.2.0
• weather_status: 1.8.0
• workflowengine: 2.10.0
  Disabled:
• admin_audit
• carnet: 0.25.4
• encryption
• files_external
• files_rightclick: 1.6.0
• mail: 3.5.7
• twofactor_totp
• unsplash: 2.2.1
• user_ldap

Nextcloud configuration:

{
"instanceid": "REMOVED SENSITIVE VALUE",
"passwordsalt": "REMOVED SENSITIVE VALUE",
"secret": "REMOVED SENSITIVE VALUE",
"trusted_domains": [
"REMOVED SENSITIVE VALUE"
],
"datadirectory": "REMOVED SENSITIVE VALUE",
"dbtype": "mysql",
"version": "28.0.3.2",
"overwrite.cli.url": "REMOVED SENSITIVE VALUE",
"dbname": "REMOVED SENSITIVE VALUE",
"dbhost": "REMOVED SENSITIVE VALUE",
"dbport": "",
"dbtableprefix": "oc_",
"mysql.utf8mb4": true,
"dbuser": "REMOVED SENSITIVE VALUE",
"dbpassword": "REMOVED SENSITIVE VALUE",
"installed": true,
"logtimezone": "Europe/Amsterdam",
"maintenance": false,
"loglevel": 0,
"filesystem_check_changes": 1,
"memcache.local": "\OC\Memcache\Redis",
"redis": {
"host": "REMOVED SENSITIVE VALUE",
"port": 6379
},
"memcache.locking": "\OC\Memcache\Redis",
"mail_smtpmode": "sendmail",
"mail_smtpauthtype": "LOGIN",
"mail_from_address": "REMOVED SENSITIVE VALUE",
"mail_domain": "REMOVED SENSITIVE VALUE",
"theme": "",
"has_rebuilt_cache": true,
"default_phone_region": "IT",
"versions_retention_obligation": "auto,90",
"trashbin_retention_obligation": "auto,30",
"updater.release.channel": "stable"
}

Are you using an external user-backend, if yes which one: No

[MoonRubles]

I also have this problem. Probably once a day i will lose focus, start typing, including the letter A, which archives a card, and then i have to go figure out if any were archived. So hopefully keyboard shortcuts can also be disable which compounds the focus problem.

[pschopen]

I also have this problem. Probably once a day i will lose focus, start typing, including the letter A, which archives a card, and then i have to go figure out if any were archived. So hopefully keyboard shortcuts can also be disable which compounds the focus problem.

This especially is problematic and has happened to me a couple of times already, too.

[docjyJ]

I also don't understand Deck shortcuts. Why not use key combinations? Every time I lose focus, I take involuntary actions...

[leadermontanus]

Happens repeatedly after I upgraded to latest version of Deck.

[jgardner7289]

Thanks for making the report, this issue has been driving me insane. Currently on Nextcloud 28.0.5. +1 to the idea that keyboards shortcuts should be key combinations, it is far to easy to take unintended actions in Deck even outside the context of this bug.