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

Branch dropdown menu does not work #3314

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

Originally created by @kgraefe on GitHub (May 10, 2019).

  • Gitea version (or commit ref): 1.8.1 built with go1.12.5 (linux-arm-6)
  • Git version: 2.11.0
  • Operating system: Debian GNU/Linux 9.8 (stretch)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When clicking on the branches drop down the menu does not open. The arrow gets an arrow and nothing more happens.

I see 18 warnings in the javascript console: jquery.min.js:3 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952 but that's all.

Also in the source tree there's only the master branch although this repository has multiple branches.

I cannot reproduce that on https://try.gitea.io so it seems be an issue of my instance. But I don't know how to tackle it.

Screenshots

gitea-branches-dropdown
gitea-branches-dropdown-source

Originally created by @kgraefe on GitHub (May 10, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.8.1 built with go1.12.5 (linux-arm-6) - Git version: 2.11.0 - Operating system: Debian GNU/Linux 9.8 (stretch) - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [X] No - [ ] Not relevant - Log gist: ## Description When clicking on the branches drop down the menu does not open. The arrow gets an arrow and nothing more happens. I see 18 warnings in the javascript console: `jquery.min.js:3 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952` but that's all. Also in the source tree there's only the master branch although this repository has multiple branches. I cannot reproduce that on https://try.gitea.io so it seems be an issue of my instance. But I don't know how to tackle it. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> ![gitea-branches-dropdown](https://user-images.githubusercontent.com/3797324/57524861-652fde00-7329-11e9-8f7a-5fb0e95e9893.png) ![gitea-branches-dropdown-source](https://user-images.githubusercontent.com/3797324/57524863-652fde00-7329-11e9-90d7-c934698f998f.png)
GiteaMirror added the issue/needs-feedback label 2025-11-02 05:07:50 -06:00
GiteaMirror commented 2025-11-02 05:07:51 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (May 15, 2019):

Do you see any errors in gitea.log?

@lafriks commented on GitHub (May 15, 2019): Do you see any errors in gitea.log?
GiteaMirror commented 2025-11-02 05:07:51 -06:00
Author
Owner
Copy Link

@kgraefe commented on GitHub (May 15, 2019):

Unfortunately not. With log.LEVEL=Debug it just gives:

2019/05/15 13:13:22 [I] Log Mode: File(Debug)
2019/05/15 13:13:22 [I] XORM Log Mode: File(Debug)
2019/05/15 13:13:22 [I] Cache Service Enabled
2019/05/15 13:13:22 [I] Session Service Enabled
2019/05/15 13:13:22 [I] Beginning ORM engine initialization.
2019/05/15 13:13:22 [I] ORM engine initialization attempt #1/10...
2019/05/15 13:13:23 [I] ORM engine initialization successful!
2019/05/15 13:13:24 [I] Git Version: 2.11.0
2019/05/15 13:13:24 [I] SQLite3 Supported
2019/05/15 13:13:24 [I] Run Mode: Production
2019/05/15 13:13:29 [I] Listen: http://0.0.0.0:3000
2019/05/15 13:13:32 [D] Session ID: xxxxxxxxxxxxxxxx
2019/05/15 13:13:32 [D] CSRF Token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX==
2019/05/15 13:13:32 [D] Template: pwa/serviceworker_js
2019/05/15 13:13:40 [D] Session ID: xxxxxxxxxxxxxxxx
2019/05/15 13:13:40 [D] CSRF Token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX==
2019/05/15 13:13:41 [D] Template: repo/home
2019/05/15 13:13:41 [D] Session ID: xxxxxxxxxxxxxxxx
2019/05/15 13:13:41 [D] CSRF Token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX==
2019/05/15 13:13:41 [D] Template: pwa/manifest_json
2019/05/15 13:13:43 [D] Session ID: xxxxxxxxxxxxxxxx
2019/05/15 13:13:43 [D] CSRF Token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX==
2019/05/15 13:13:43 [D] Template: pwa/serviceworker_js
@kgraefe commented on GitHub (May 15, 2019): Unfortunately not. With `log.LEVEL=Debug` it just gives: ``` 2019/05/15 13:13:22 [I] Log Mode: File(Debug) 2019/05/15 13:13:22 [I] XORM Log Mode: File(Debug) 2019/05/15 13:13:22 [I] Cache Service Enabled 2019/05/15 13:13:22 [I] Session Service Enabled 2019/05/15 13:13:22 [I] Beginning ORM engine initialization. 2019/05/15 13:13:22 [I] ORM engine initialization attempt #1/10... 2019/05/15 13:13:23 [I] ORM engine initialization successful! 2019/05/15 13:13:24 [I] Git Version: 2.11.0 2019/05/15 13:13:24 [I] SQLite3 Supported 2019/05/15 13:13:24 [I] Run Mode: Production 2019/05/15 13:13:29 [I] Listen: http://0.0.0.0:3000 2019/05/15 13:13:32 [D] Session ID: xxxxxxxxxxxxxxxx 2019/05/15 13:13:32 [D] CSRF Token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX== 2019/05/15 13:13:32 [D] Template: pwa/serviceworker_js 2019/05/15 13:13:40 [D] Session ID: xxxxxxxxxxxxxxxx 2019/05/15 13:13:40 [D] CSRF Token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX== 2019/05/15 13:13:41 [D] Template: repo/home 2019/05/15 13:13:41 [D] Session ID: xxxxxxxxxxxxxxxx 2019/05/15 13:13:41 [D] CSRF Token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX== 2019/05/15 13:13:41 [D] Template: pwa/manifest_json 2019/05/15 13:13:43 [D] Session ID: xxxxxxxxxxxxxxxx 2019/05/15 13:13:43 [D] CSRF Token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX== 2019/05/15 13:13:43 [D] Template: pwa/serviceworker_js ```
GiteaMirror commented 2025-11-02 05:07:51 -06:00
Author
Owner
Copy Link

@kgraefe commented on GitHub (May 28, 2019):

It turned out to be my Apache reverse proxy configuration. I had SetOutputFilter INFLATE;proxy-html;DEFLATE which apparently breaks the menu.

@kgraefe commented on GitHub (May 28, 2019): It turned out to be my Apache reverse proxy configuration. I had `SetOutputFilter INFLATE;proxy-html;DEFLATE` which apparently breaks the menu.
GiteaMirror commented 2025-11-02 05:07:52 -06:00
Author
Owner
Copy Link

@waltervanzellaGVT commented on GitHub (Jan 7, 2020):

It turned out to be my Apache reverse proxy configuration. I had SetOutputFilter INFLATE;proxy-html;DEFLATE which apparently breaks the menu.

I am having a similar problem, as reported in issue #9569.
I am a newby on these topics and I have no idea what to do. Where can I find these Apache configuration file? and what did you change in order to solve ?
Thank you.
W.

@waltervanzellaGVT commented on GitHub (Jan 7, 2020): > > > It turned out to be my Apache reverse proxy configuration. I had `SetOutputFilter INFLATE;proxy-html;DEFLATE` which apparently breaks the menu. I am having a similar problem, as reported in issue #9569. I am a newby on these topics and I have no idea what to do. Where can I find these Apache configuration file? and what did you change in order to solve ? Thank you. W.
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 issue/needs-feedback
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#3314
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?