-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Improve "generate new access token" form #33730
Conversation
Thank you very much! It is much clearer than before. And by the way, there is a |
Both comments have been processed. |
For the future, consider using a different source branch name than |
1f77ce3
to
bf6f2db
Compare
-webkit-mask-image: var(--octicon-chevron-right); | ||
transform: rotate(90deg); /* point the chevron down */ | ||
background: currentcolor; | ||
} |
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.
@wxiaoguang is this not needed anymore? I recall this class is for "nicer" select boxes with chevron etc, but I think some browser may by default render chevrons as seen in screenshots in #33434, but I'm not sure all of them do.
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.
No code uses it.
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.
Right, it was a single use. I will check if I need to re-introduce it for #33434.
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.
I guess no ....
We already have "ui dropdown (selection)", or just use the browser native "select". I think we'd better avoid too much "customization".
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.
Yeah this was a minor enhancement for the native select, because I think those will render differently based on browser OS, but I will check again if it's really needed.
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.
Do you mean you need to check before merging this PR, or we could merge this PR if no other problem and leave the "check" to the future?
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.
No, merge this now.
Move the “Generate New Token” button to the top of the token list for better accessibility. Currently, users with multiple tokens must scroll to the bottom each time they need to generate a new one, which is inconvenient. Placing it at the top improves efficiency and usability. |
I see where you are coming from, but placing the button on top would be inconsistent with other similar forms. |
I believe it’s consistent. Most list pages feature a ‘New’ button in the top right corner, which either switches the view or opens a form window. I’ve never seen a ‘New’ button placed at the bottom of a list. |
This could be another PRs since this is not the last place putting the button at the bottom. |
I was unable to create a backport for 1.23. @gsvd, please send one manually. 🍵
|
Does it really need a backport? |
* giteaofficial/main: Use pullrequestlist instead of []*pullrequest (go-gitea#33765) Upgrade act to 0.261.4 and actions-proto-go to v0.4.1 (go-gitea#33760) Webhook add X-Gitea-Hook-Installation-Target-Type Header (go-gitea#33752) Fix dynamic content loading init problem (go-gitea#33748) [skip ci] Updated translations via Crowdin Add composor source field (go-gitea#33502) upgrade go-crypto from 1.1.5 to 1.1.6 (go-gitea#33745) Disable go license generation as part of `make tidy` (go-gitea#33747) Refactor repo-diff.ts (go-gitea#33746) Use `git diff-tree` for `DiffFileTree` on diff pages (go-gitea#33514) [skip ci] Updated translations via Crowdin Improve "generate new access token" form (go-gitea#33730) Remove superflous tw-content-center (go-gitea#33741) Clone repository with Tea CLI (go-gitea#33725) allow filtering /repos/{owner}/{repo}/pulls by target base branch queryparam (go-gitea#33684) Show info about maintainers are allowed to edit a PR (go-gitea#33738) Improve admin user view page (go-gitea#33735) [skip ci] Updated translations via Crowdin Align sidebar gears to the right (go-gitea#33721)
Fix: #33519
As discussed in PR #33614, the ScopedAccessTokenSelector Vue component is not particularly useful.
This PR removes the component and reverts to using HTML templates. It also introduces some (hopefully) useful refactoring.
The Vue component was causing the UX bug reported in the linked issue. Required form fields are now properly working, as expected (see screenshot).