github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-15 20:52:52 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Add deploy key should scroll down to the form #7893

New Issue
Closed
opened 2025-11-02 07:40:43 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 07:40:43 -06:00
Owner
Copy Link

Originally created by @GhaziTriki on GitHub (Sep 24, 2021).

Gitea Version

1.15.0

Operating System

Windows 10 Pro

Browser Version

Firefox 92.0

Can you reproduce the bug on the Gitea demo site?

Yes

Description

When clicking on "Add Deploy Key" you have a long list of keys, the form is displayed at the most bottom and we have to manually scroll. The button should show the form and scroll to it without any additional efforts.

Screenshots

image

Originally created by @GhaziTriki on GitHub (Sep 24, 2021). ### Gitea Version 1.15.0 ### Operating System Windows 10 Pro ### Browser Version Firefox 92.0 ### Can you reproduce the bug on the Gitea demo site? Yes ### Description When clicking on "Add Deploy Key" you have a long list of keys, the form is displayed at the most bottom and we have to manually scroll. The button should show the form and scroll to it without any additional efforts. ### Screenshots ![image](https://user-images.githubusercontent.com/4991088/134663579-ea66d993-20cd-46d1-8728-ad315b10ef1c.png)
GiteaMirror added the topic/uitype/proposal labels 2025-11-02 07:40:43 -06:00
GiteaMirror commented 2025-11-02 07:40:44 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Sep 24, 2021):

I think a better approach would be to move the form before the list of already present keys.
That would solve this problem just as well as scrolling down automatically and can be implemented easier and less error-prone than the automatic scroll.

@delvh commented on GitHub (Sep 24, 2021): I think a better approach would be to move the form before the list of already present keys. That would solve this problem just as well as scrolling down automatically and can be implemented easier and less error-prone than the automatic scroll.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/ui type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7893
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?