This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Can no longer scroll with mouse since FF48 on Android. FF48 now marks text instead of scrolling

  • 6 antwoorde
  • 17 hierdie probleem
  • 7 views
  • Laaste antwoord deur Kevin

fox4ever
fox4ever
more options

Subject says it all.

I have two MyGica Android boxes running FF48 one with Android 4.4.2 and the other is 5.0. Never had issues with FF until V48.

Now I can't scroll with remote mouse nor keyboard.

Subject says it all. I have two MyGica Android boxes running FF48 one with Android 4.4.2 and the other is 5.0. Never had issues with FF until V48. Now I can't scroll with remote mouse nor keyboard.

Gekose oplossing

Temporary fix for me was to downgrade to v47.0 using titanium backup...

Lees dié antwoord in konteks 👍 1

All Replies (6)

FadeFx
FadeFx
more options

Gekose oplossing

Temporary fix for me was to downgrade to v47.0 using titanium backup...

fox4ever
fox4ever Vraag-eienaar
more options

I did the same as a workaround. Also reported it on bugzilla.

FadeFx
FadeFx
more options

Also i can not start most embedded videos nor fullscreen them by doubleclick. Seems somehow related.

zygdresze
zygdresze
more options

I have the same problem with FF48 and FF49 now.

fox4ever
fox4ever Vraag-eienaar
more options

zygdresze said

I have the same problem with FF48 and FF49 now.

I think you found that thread https://bugzilla.mozilla.org/show_bug.cgi?id=1294707

Bug fixed in 52.0.1 Nightly

Kevin
Kevin
  • Moderator
more options

More accurately this is fixed in Firefox 50. This release will be in the Play store on Nov 15th.

The fix was first part of Firefox 52 and then the fix was moved forward to 51 and 50.

Gewysig op deur Kevin