Hamburger menu on firefox mobile will not expand #12553

New Issue

GiteaMirror · 2025-11-02T10:13:50-06:00

GiteaMirror commented

2025-11-02 10:13:50 -06:00

Originally created by @shrapnelnet on GitHub (Feb 27, 2024).

Description

I am running a self hosted gitea instance. On testing, I've found that the hamburger menu fails to open within firefox, but remains working on safari.

This makes it impossible to navigate on mobile without directly writing the URI into the search bar.

Gitea Version

1.22.0+dev-849-g324626a11

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

2.34.1

Operating System

5.15.0-94-generic Ubuntu aarch64 GNU/Linux

How are you running Gitea?

Gitea is being run in a tmux instance via a VPS. I built via source

Database

PostgreSQL

Originally created by @shrapnelnet on GitHub (Feb 27, 2024). ### Description I am running a self hosted gitea instance. On testing, I've found that the hamburger menu fails to open within firefox, but remains working on safari. This makes it impossible to navigate on mobile without directly writing the URI into the search bar. ### Gitea Version 1.22.0+dev-849-g324626a11 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.34.1 ### Operating System 5.15.0-94-generic Ubuntu aarch64 GNU/Linux ### How are you running Gitea? Gitea is being run in a tmux instance via a VPS. I built via source ### Database PostgreSQL

GiteaMirror added the issue/needs-feedback type/bug labels 2025-11-02 10:13:50 -06:00

GiteaMirror closed this issue

2025-11-02 10:13:51 -06:00

GiteaMirror commented

2025-11-02 10:13:51 -06:00

@lunny commented on GitHub (Feb 27, 2024):

Did you mean your web browser is mobile firefox?

@lunny commented on GitHub (Feb 27, 2024): Did you mean your web browser is mobile firefox?

GiteaMirror commented

2025-11-02 10:13:52 -06:00

@shrapnelnet commented on GitHub (Feb 27, 2024):

Did you mean your web browser is mobile firefox?

sorry if this is unclear, firefox desktop works absolutely fine, but if i visit on mobile on firefox the menu will not expand on click which is the intended behaviour.

this behaviour is also true for the demo page

@shrapnelnet commented on GitHub (Feb 27, 2024): > Did you mean your web browser is mobile firefox? sorry if this is unclear, firefox desktop works absolutely fine, but if i visit on mobile on firefox the menu will not expand on click which is the intended behaviour. this behaviour is also true for the demo page

GiteaMirror commented

2025-11-02 10:13:52 -06:00

@wxiaoguang commented on GitHub (Feb 28, 2024):

the hamburger menu fails to open within firefox,

What is a "hamburger menu"? Could you show a screenshot?

@wxiaoguang commented on GitHub (Feb 28, 2024): > the hamburger menu fails to open within firefox, What is a "hamburger menu"? Could you show a screenshot?

GiteaMirror commented

2025-11-02 10:13:52 -06:00

@silverwind commented on GitHub (Feb 28, 2024):

They probably mean the menu in the navbar, right? It's a plain <button> with an onClick handler, I fail to see how this could fail to work, at least not without displaying a JS error. Maybe hook up some remote devtools to inspect the browser console.

@silverwind commented on GitHub (Feb 28, 2024): They probably mean the menu in the navbar, right? It's a plain `<button>` with an `onClick` handler, I fail to see how this could fail to work, at least not without displaying a JS error. Maybe hook up some remote devtools to inspect the browser console.

GiteaMirror commented

2025-11-02 10:13:52 -06:00

@shrapnelnet commented on GitHub (Feb 28, 2024):

They probably mean the menu in the navbar, right? It's a plain <button> with an onClick handler, I fail to see how this could fail to work, at least not without displaying a JS error. Maybe hook up some remote devtools to inspect the browser console.

yes, this is correct.

i fail to see too! cross browser compatibility is excellent nowadays especially for something as simple as event handlers and i am not quite sure why this would happen whatsoever. i will debug soon and let you know

@shrapnelnet commented on GitHub (Feb 28, 2024): > They probably mean the menu in the navbar, right? It's a plain `<button>` with an `onClick` handler, I fail to see how this could fail to work, at least not without displaying a JS error. Maybe hook up some remote devtools to inspect the browser console. yes, this is correct. i fail to see too! cross browser compatibility is excellent nowadays especially for something as simple as event handlers and i am not quite sure why this would happen whatsoever. i will debug soon and let you know

GiteaMirror commented

2025-11-02 10:13:52 -06:00

@charles7668 commented on GitHub (Feb 29, 2024):

They probably mean the menu in the navbar, right? It's a plain <button> with an onClick handler, I fail to see how this could fail to work, at least not without displaying a JS error. Maybe hook up some remote devtools to inspect the browser console.

yes, this is correct.

i fail to see too! cross browser compatibility is excellent nowadays especially for something as simple as event handlers and i am not quite sure why this would happen whatsoever. i will debug soon and let you know

Firefox on mobile devices can install extensions. Perhaps you have installed an extension like "NoScript"?

@charles7668 commented on GitHub (Feb 29, 2024): > > They probably mean the menu in the navbar, right? It's a plain `<button>` with an `onClick` handler, I fail to see how this could fail to work, at least not without displaying a JS error. Maybe hook up some remote devtools to inspect the browser console. > > yes, this is correct. > > i fail to see too! cross browser compatibility is excellent nowadays especially for something as simple as event handlers and i am not quite sure why this would happen whatsoever. i will debug soon and let you know Firefox on mobile devices can install extensions. Perhaps you have installed an extension like "NoScript"?

GiteaMirror commented

2025-11-02 10:13:53 -06:00

@GiteaBot commented on GitHub (Apr 12, 2024):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Apr 12, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#12553