Firefox for Android Support Forum

Firefox Nightly 110.0a1 (Build #2015925675), Sony Xperia 1 mk3, 61.2.A.0.382 release-keys Android 13

Been having issues with the refresh gesture, namely it activating when just trying to scroll up the page.

I'm not certain of the proper behaviour, but I've had pull down to refresh initiate with all kinds of downward swipes; fast, slow, short and long; and in various locations on the screen; centre, sides (close enough to also start back gesture), lower third; and even seen it wanting to refresh when simply tapping to stop inertia scroll, as well as when pressing and holding to keep screen alive for seconds before pulling down to return to the top.

Noticing it initiate, then releasing upward to cancel, then repeating the previous downward swipe intermittently triggers it again; sometimes it's gone, sometimes it triggers another once or twice, and one time it just would not stop and I couldn't scroll up the page no matter where on the screen I began to swipe down.

I'm presuming it's only meant to activate in upper third or even quarter, but regardless, this is a relatively recent (several days to a week, idk) issue that I'm dealing with, although it has become rife tonight.

Some websites seem better than others, and I was considering it was a fault of some designs, but alas I couldn't find any spots where I could consistently get it to happen; not even dragging from the top of the screen is working right now, so I have no idea what's going on.

https://ok2fly.com.au/ was a nightmare; tap anywhere to open a pop-up, scroll to bottom, then try to scroll up. I've got a great little screen record to demonstrate how inconsistent it is, if anyone wants.

Lemme know if there's anything else I can do to help diagnose this.

Hi,

We use about ten Android tablets running Firefox in our shop for our employees to enter on a webpage daily some informations. Tablets are programmed to keep display active 24h/7d, firefox is pinned so the app stay opened and users don't go to other app. The extension LeechBlock NG prevent users from accessing other webistes. Everything work well except on mondays morning.

Without fault first person to try to connect on the website will see the app crash to the desktop. Since the app is pinned user will have to wait for a supervisor to come in and unpin the crashed (and invisible) app, re-launch it and pin it. Then it will work all week without issue as long as the tablet is used at least once a day. We recently added a new tablet which is used less than others and that one does crash during the week but never twice in same day. Here's the crash report that we have (I checked multiples tablets and they all share the same crash code):

99526033-8b07-4d48-9ea2-bf4b81157f56 mozilla.appservices.places.uniffi.PlacesApiException$UnexpectedPlacesException: reason=Invalid metadata observation: Observed view time is invalid (too long)

mozilla.appservices.places.uniffi.PlacesApiException$UnexpectedPlacesException: reason=Invalid metadata observation: Observed view time is invalid (too long)

at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.read(places.kt:21)
at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.read(places.kt:1)
at mozilla.appservices.places.uniffi.FfiConverter$DefaultImpls.liftFromRustBuffer(places.kt:13)
at mozilla.appservices.places.uniffi.FfiConverterRustBuffer$DefaultImpls.liftFromRustBuffer(places.kt:6)
at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.liftFromRustBuffer(places.kt:2)
at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.liftFromRustBuffer(places.kt:1)
at mozilla.appservices.places.uniffi.FfiConverterRustBuffer$DefaultImpls.lift(places.kt:7)
at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.lift(places.kt:3)
at mozilla.appservices.places.uniffi.FfiConverterTypePlacesApiError.lift(places.kt:2)
at mozilla.appservices.places.uniffi.PlacesApiException$ErrorHandler.lift(places.kt:2)
at mozilla.appservices.places.uniffi.PlacesApiException$ErrorHandler.lift(places.kt:1)
at mozilla.appservices.places.uniffi.PlacesConnection.noteHistoryMetadataObservation(places.kt:162)
at mozilla.appservices.places.PlacesWriterConnection.noteHistoryMetadataObservation(PlacesConnection.kt:19)
at mozilla.components.browser.storage.sync.PlacesHistoryStorage$noteHistoryMetadataObservation$2.invokeSuspend(PlacesHistoryStorage.kt:63)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:107)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@57af652, java.util.concurrent.Executors$FinalizableDelegatedExecutorService@1d40d23]

Wondering if someone can help me decypher this to fix/prevent it. Is it the extension or browser itself that cause the crash if the page hasn't changed long enough? Thanks for suggestions (I will not consider "have you tried without the extension" as a valid suggestion)

Hello,

I choose to use FireFox when viewing video content. Only I have this persistent issue when I'm watching/listening a video/podcast and I need to goto a different Tab/Page or use an App or perform a different task, when I return to the tab with paused video it will reload and then the video page will refresh or re-open back to the video list/menu. This causes me to lose my position in the timeline and must find my place again manually. I've noticed this happens after a certain amount of time has passed, not much though, like 60 seconds or so, maybe more. This is frustrating and time consuming and I've noticed this doesn't occur in many chromium based browsers. That said, I strive to avoid google altogether and would rather stick it out with Firefox.

Thank you for reading my question, any advice is appreciated.

113.1.0 (Build #2015950737), 52a200d213+ GV: 113.0.1-20230511191846 AS: 97.4.1 2023-05-15T18:19:10.974886

Had a persistent issue where firefox wont display a video inside the bounds of the player For example the attached images show the same video on firefox and opera. opera shows the entire video where as firefox only shows the top left hand corner This has been an issue since the fix for youtube videos having the opposite issue was release Firefox for Android v112.1.0 Android v10

I just updated to 113.2.0. When viewing a YouTube video then going to full screen landscape mode it still intermittently minimises Firefox, and when I go back to you tube the formatting is all confused I have to close Firefox and reopen. On a Google Pixel 7 Pro phone.

Hi, I have the latest firefox on my Samsung A54 5G (and previously on my A71). I'll open firefox, do a few searches and eventually I'll do a search and firefox goes back to the last search results and does NOT show any links related to the new search. If I kill firefox and restart it, it works again. The problem is more irritating than it might sound because it seems to happen too frequently when I am trying to look something up - but when I try to reproduce the issue it's hard to reproduce. The key element may be that I need to have firefox open and idel for a while before the problem occurs. Any advice is welcome!

When attempting to enter full screen mode on Firefox for Android, and to get into landscape mode, the browser appears to crash, keeps audio playing, and "entering full screen mode" dialogue pops up. Have to open Firefox again, and can only be viewed in landscape mode while session is continued. To return to non-landscape mode, the app needs to be force stopped, otherwise you only get to see the left one third side of any web page you navigate to. Seems to have started with most recent update. Is there any way to fix?

Hey there,

As the title suggests, I'm having an issue with the navigation bar. It remains at the bottom of the screen even when I have the least need for it, which makes the content of the screen glitchy. It may not sound like much, but it's very annoying and ruins the whole browsing experience, especially when watching videos. Because of the unwanted navigation bar, even a slight touch on the screen causes the videos or pages, but mostly videos, to move around left and right when in landscape mode. As you can see in one of the screenshots I sent, the video is not even visible, it's just a black screen, which is a different issue that I faced for the first time but I am not sure how often I'll get that in future but it's there.

If anyone can suggest a fix for this issue,(the one with the navigation bar and jumpy video screen) such as a setting that I can turn on or off to get rid of the navigation bar, it would be greatly appreciated.

Just updated to latest version of Firefox for Android (ver 113). When I try to watch a YouTube video in full screen, the app suddenly closes, as if I pressed the home button (note: I say "close" rather than "crash" because when I reopen it, all the pages are still loaded). This doesn't happen every time, but it is annoying. Is there any way to fix this?

All sorts of video on my Firefox Android is unable to play, as in they load indefinitely, only show the initial frame and never play. Nothing happens when I tap the play button. The progress bar on videos does move, so it's likely not a connection issue. It's not only on YouTube, any video and stream on any website has the same issue. I have enabled autoplay, deleted cookies, disabled add-ons but nothing helps.

When reading the site https://hellasjournal.com after a while Firefox freezes and crashes. It's not a site problem because with Chrome works fine.

Dear friends,

My mobile phone is OnePlus 8 Pro. ColorOS 13.0/Android 13. Firefox ver 111.1.1. My earphone is SONY WI-1000XM2.

When Youtube videos were playing in firefox Android, it always paused for a minute when following events happened:

• switch on/off my earphone
• end an incoming call

it seems Firefox takes long time to get back the audio output device. Chrome takes just one second to reconnect the audio device.