Firefox For Android On Phone doesn't respond to Taps
I almost always have to tap multiple times....like 7 or 8 times ... to get a link to open. This happens on almost all sites...google, mozilla.org, my own site. Responses are immediate if I go into FireFox settings and tap around. Also, all other taps are immediate...like mail, calculator, etc. That includes tapping a link in an email. The page will open with one tap but then any links on the page will take many taps.
The phone is a Sony Model G8441 running Android 9. Build number 47.2.A.11.228
Vahaolana nofidina
Yippie, I just installed 84.1.1 and I am no longer experiencing the "non-response" problem. Every tap on a link is as snappy as on Chrome. I had switched to Chrome because I couldn't use FireFox because of frustration.
Hamaky an'ity valiny ity @ sehatra 👍 0All Replies (5)
I still have this problem. I tried clearing the cache and data but that didn't help. That prompted me to enable the chrome browser that was on my phone. It is great, really snappy. One tap and it does the right thing. FireFox still requires 6...7...or 8 taps to make something happen.
I really don't want to use Chrome......google knows too much about me already. Can it be some settings that cause this? What can I do?
Hi
What version of Firefox for Android do you have installed on your device?
I don't know what it was when I first had the problem but I have been trying to get it to work so I uninstalled it and reinstalled it from the play store. It still has the problem. For example, even the moz://a Support page, Frequent topics, Basic browsing took 6 or 7 taps.
Version 83.1.0 Build #2015776403 AC: 63.0.9,fc54c566e GV: 83.0-202011112153044 AS:63.0.0 Wednesday 11/18 @ 6:23 PM
Hi
I am sorry to hear that this is happening. I can see that our developers are aware of this issue and I hope that it can be resolved very soon.
Vahaolana Nofidina
Yippie, I just installed 84.1.1 and I am no longer experiencing the "non-response" problem. Every tap on a link is as snappy as on Chrome. I had switched to Chrome because I couldn't use FireFox because of frustration.