Ngwaahịa Niile Community Forum

I switched to a Samsung u24+ from a OnePlus phone and when browsing, if I go back to the previous page and then touch anywhere in the top half of the screen, firefox incorrectly thinks I have executed the refresh gesture of swiping down from the top. It does not happen if I wait a few seconds before touching the screen after going to the previous page.

This is very annoying and seems to be a longstanding 3 year old bug on Motorola and Samsung devices.

I have no clue as to how we are supposed to be able to get around on the mobile version. There's no back or forward buttons, not even a close page function, other than closing the app, but when it opens, the same page is there! How is anyone supposed to navigate while using this?? I don't see a menu button, or preferences button, how is this a functional browser?

Using Firefox 157.0.1. , Windows 10 Pro. When I right click one of the menu items I get is ""Open link in new tab". This has always worked - keeping the current tab open and opening the link in a new tab. When I click on that now it opens the link I want to go to but then closes and replaces current tab. Is this a new "feature"? Please email [redacted email from community support forum]

Currently, using web browsers on Android TV is a frustrating experience. Most available TV browsers lack proper extension support (such as uBlock Origin), leaving users exposed to aggressive ads, trackers, and intrusive pop-ups on a 10-foot interface.

Additionally, standard TV browsers struggle with long-form video playback. Without the ability to route video streams to external native players (like ExoPlayer or Just Player), users miss out on Automatic Refresh Rate and Resolution Matching. This results in persistent video judder/stuttering issues due to mismatched display frame rates (e.g., playing 24fps content on a 60Hz fixed TV lock).

Hello,

I’m the developer of SnakeGame.Live , a browser-based multiplayer snake game with mouse steering on desktop.

I would like to understand the difference between Firefox’s F11 fullscreen mode and fullscreen activated through a website’s Fullscreen API.

For a mouse-controlled game, do these modes behave differently when the pointer reaches the top edge of the screen? Is there a recommended way to let players use fullscreen while keeping Firefox’s normal exit controls available?

I’m using Windows 10. I would appreciate guidance on the expected Firefox behavior and any relevant support documentation.

Thank you.

Does Mozilla plan to optimise Firefox on Android for Desktop devices given that the Googlebook OS was released? It is currently very difficult to use given that I can't select text on webpages, also there's no context menu when right clicking.

Los videos de YouTube no se reproducen correctamente en Firefox. Algunos videos no cargan o se quedan congelados y no puedo verlos normalmente. Ya intenté actualizar la página, pero el problema continúa. Quisiera saber cómo puedo solucionarlo.