After tapping certain page elements, the next time I touch the screen, it starts as if I've dragged my finger down, causing the page to refresh if I let go without first dragging my finger up to undo it
Categories
(Firefox for Android :: Browser Engine, defect)
Tracking
()
People
(Reporter: shelbyoldfield97, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (Android 14; Mobile; rv:137.0) Gecko/137.0 Firefox/137.0
Firefox for Android
Steps to reproduce:
Touching certain UI elements on websites (it happens on numerous websites), usually like a button, will cause the next time I touch the screen to be treated like I've swiped down (even though I've merely touched my finger to the screen), displaying the refresh arrow at the top of the screen.
Actual results:
Releasing my finger (e.g., say I try to tap another UI element) will cause the page to refresh, as is typical when swiping down in Firefox...except I didn't swipe down. Also, swiping up before releasing my finger does undo it, so I can workaround the issue if I know it's going to happen, or notice the refresh arrow at the top before removing my finger. But often, I unintentionally refresh the page, losing data in the process.
Expected results:
Nothing? Just the tap? It shouldn't be treating my next tap as if I dragged down, causing accidental page refreshes.
|
||
Comment 1•7 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox for Android::Browser Engine' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•6 months ago
|
||
(In reply to Shelby Oldfield from comment #0)
Touching certain UI elements on websites (it happens on numerous websites), usually like a button, will cause [...]
I know you mention it occurs on numerous websites, but if you could provide a specific example of a website + UI element, that would help further diagnosis of the issue.
|
||
Comment 3•6 months ago
|
||
I'm having the same issue; the biggest culprit is the (new) Reddit mobile website, but it's not reliably reproducible.
It often happens on the first interaction after opening the home page. It also can happen after clicking on a post thumbnail to preview it, then clicking X to close the preview, then the next tap is interpreted as a swipe-to-refresh, as described.
If I can identify another common culprit, I will report back.
Description
•