7dc453bb39
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. |
||
|---|---|---|
| .. | ||
| fomantic | ||
| dirauto.js | ||
| fetch.js | ||
| fetch.test.js | ||
| fomantic.js | ||
| sortable.js | ||
| stores.js | ||
| tippy.js | ||
| toast.js | ||
| toast.test.js | ||