-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Set manual tabindex
es on login page
#31689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
tabindex
es on login page
The only way I'll approve this PR as it is is if you document somewhere in that file exactly why we have this weird tab order. |
Yes, I thought about adding a comment so this does not break during refactoring. I don't think it's weird, it's more like "optimized for usability" and the position for the forgot link is ideal and follows what other login forms do as well. |
I meant for someone who looks over the code and hasn't seen this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not blocking the PR, just having this here so that it doesn't get merged prior to the merger going through the comments. feel free to dismiss this once discussion is complete
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* giteaofficial/main: Fix incorrect `/tokens` api (go-gitea#32085) Set manual `tabindex`es on login page (go-gitea#31689) Only use Host header from reverse proxy (go-gitea#32060) [skip ci] Updated translations via Crowdin
Fixes #31686.
A more elborate manual tabindex numbering could be done, but I think it's not really worth the extra effort and such stuff could easily break during refactors.
Includes another small tweak to un-stretch the
<a>
element so it's only as large as it needs to be and this change also made the margin unneeded.