forgejo-federation/web_src/js/modules
Otto Richter 7dc453bb39 Remove inputs in dropdowns from taborder
Inputs are normally present in the taborder of a website. When they are
inside a dropdown, this means a user could theoretically also tab
through them.

With the current dropdown approach, however, this can result in the
focus being trapped, because the dropdown is closed after the focus
switches to the next element.

In this case, the focus moves to the end of the page, breaking keyword
navigation and making parts of the page inaccessible with a keyboard.

I was only able to reproduce this in Firefox.

This patch removes inputs inside dropdowns from taborder. It should be
generally safe even with potential side-effects, because *nothing*
inside dropdowns should be in the tab order.

This is a hotfix for https://codeberg.org/forgejo/forgejo/issues/2635,
but I acknowledge it is not an ideal solution.
2024-03-12 02:24:17 +01:00
..
fomantic Remove inputs in dropdowns from taborder 2024-03-12 02:24:17 +01:00
dirauto.js [gitea] Avoid showing unnecessary JS errors when there are elements with different origin on the page (#29081) 2024-02-10 10:53:43 +01:00
fetch.js Refactor request function (#29187) 2024-02-17 23:24:31 +01:00
fetch.test.js Use vitest globals (#27102) 2023-09-27 04:37:13 +00:00
fomantic.js Move some JS code from fomantic.js to standalone files (#27994) 2023-11-12 07:15:00 +00:00
sortable.js Import sortablejs only once (#25936) 2023-07-17 18:06:37 +00:00
stores.js Refactor diffFileInfo / DiffTreeStore (#24998) 2023-05-30 18:53:15 +08:00
tippy.js [gitea] Avoid showing unnecessary JS errors when there are elements with different origin on the page (#29081) 2024-02-10 10:53:43 +01:00
toast.js Make PR form use toast to show error message (#29545) 2024-03-06 12:10:46 +08:00
toast.test.js Use vitest globals (#27102) 2023-09-27 04:37:13 +00:00