[BITV]: Focus trap on search field doesn't work well

[JuliaKirschenheuter]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

This is accessibility issue.

Focus trap on search field "Search for share recipients" doesn't work well.

Steps to reproduce

Bug is only reproducible with opened photo viewer.. If viewer is closed, all focus trap and keyboard navigation working well.

1. Open any picture in files viewer
2. Open sidebar
3. Click to "sharing" tab
4. Focus on the search field "Search for share recipients"
5. Try to exit search field: Viewer with photo will be closed
6. Try to tab forwards: that doesn't work. Only tab backwards works.

Expected behavior

1. Open any picture in files viewer
2. Open sidebar
3. Click to "sharing" tab
4. Focus on the search field "Search for share recipients"
5. Try to exit search field: Viewer with photo won't be closed. Search field will be closed, but still focused.
6. Try to tab forwards: tabulation works. Next focused element would be the next element in a sidebar below search field.

Installation method

None

Nextcloud Server version

master

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[szaimen]

Cc @nextcloud/server-frontend

[rheindevde]

Exact same issue for my installation. Latest AIO-deployment, no encryption, default user backend, no fancy stuff going on.
I'm sharing via link to temporarily work around this.