Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Firefox 66 on Android 9 (Samsung Galaxy 10e) won't scroll

  • 4 Antworten
  • 5 haben dieses Problem
  • 82 Aufrufe
  • Letzte Antwort von Paul

Weitere Optionen

I've just installed Firefox for Android (v.66.0.5) from Google Play Store onto my Samsung Galaxy S10e (running Android 9). Installed OK and browser works fine, but results will not scroll vertically or horizontally. No similar problem with other apps. Is there a bug or am I missing something ?

I've just installed Firefox for Android (v.66.0.5) from Google Play Store onto my Samsung Galaxy S10e (running Android 9). Installed OK and browser works fine, but results will not scroll vertically or horizontally. No similar problem with other apps. Is there a bug or am I missing something ?

Ausgewählte Lösung

Hi

I am sorry for the delay in responding, but glad to hear this issue has been resolved.

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (4)

Weitere Optionen

Hi

That sounds a bit off and I would like to look into this further. Do you have an example URL whee this happens that I could test here?

Weitere Optionen

It happens with all URLs. Enter a search of your choice in the Firefox Home page; the results cannot be 'clicked' on to select and will not scroll in either direction. Just discovered I can 'open a link in a new tab', but the new tab has the same problems of not being able to click or scroll.

Geändert am von deggsie

Weitere Optionen

The problem is now resolved - whether as a result of the recent upgrade to Firefox v.67 or otherwise is not certain, but I can select and scroll results normally - whoopee !

Weitere Optionen

Ausgewählte Lösung

Hi

I am sorry for the delay in responding, but glad to hear this issue has been resolved.