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

'Manage Topics' will not close when text field is empty #2768

New Issue
Closed
opened 2025-11-02 04:47:47 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 04:47:47 -06:00
Owner
Copy Link

Originally created by @HeshamTB on GitHub (Jan 17, 2019).

  • Gitea version (or commit ref): 1.6.3 30560b0
  • Git version: 2.20.1
  • Operating system: Arch GNU/Linux
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • [ X ] SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • [ X ] Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

A simple bug. When in 'Code' tab in repo view, the 'Manage Topics' function can not be closed when the text field is empty unless the page is refreshed.
...

Screenshots

giteabug

Originally created by @HeshamTB on GitHub (Jan 17, 2019). - Gitea version (or commit ref): 1.6.3 30560b0 - Git version: 2.20.1 - Operating system: Arch GNU/Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ X ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ X ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description A simple bug. When in 'Code' tab in repo view, the 'Manage Topics' function can not be closed when the text field is empty unless the page is refreshed. ... ## Screenshots ![giteabug](https://user-images.githubusercontent.com/38921037/51340369-ccd2cc80-1a9f-11e9-898d-a1895d830be5.png) <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the topic/ui label 2025-11-02 04:47:47 -06:00
GiteaMirror commented 2025-11-02 04:47:49 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 21, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 21, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:47:49 -06:00
Author
Owner
Copy Link

@Ryuno-Ki commented on GitHub (Jun 5, 2022):

Cannot reproduce on try.gitea.io v 1.17.0+dev-664-g73382d213

@Ryuno-Ki commented on GitHub (Jun 5, 2022): Cannot reproduce on try.gitea.io v 1.17.0+dev-664-g73382d213
GiteaMirror commented 2025-11-02 04:47:49 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 6, 2022):

I also did a quick test, it seems that the empty input can be saved correctly by clicking "Done" button.

However, there are some UI/UX problems:

  1. Not a11y friendly (it's not an easy task because the a11y of dropdown is not supported by Fomantic UI ....)
  2. The input will only be hidden when the network request is done. If user's network is laggy or broken, then clicking "Done" will make users feel that nothing happens.

Maybe this issue can be closed and these problem desires new issues.

@wxiaoguang commented on GitHub (Jun 6, 2022): I also did a quick test, it seems that the empty input can be saved correctly by clicking "Done" button. However, there are some UI/UX problems: 1. Not a11y friendly (it's not an easy task because the a11y of dropdown is not supported by Fomantic UI ....) 2. The input will only be hidden when the network request is done. If user's network is laggy or broken, then clicking "Done" will make users feel that nothing happens. Maybe this issue can be closed and these problem desires new issues.
GiteaMirror commented 2025-11-02 04:47:49 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 13, 2023):

Thank you for reminding this issue, it has been fixed by #23626

@wxiaoguang commented on GitHub (May 13, 2023): Thank you for reminding this issue, it has been fixed by #23626
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
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#2768
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?