Closed Bug 1875698 Opened 8 months ago Closed 7 months ago

Tapping on a page sometimes causes an immediate pull-to-refresh action without pulling.

Categories

(Fenix :: General, defect)

Firefox 122
All
Android
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1872170

People

(Reporter: shardina, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Android 10; Mobile; rv:122.0) Gecko/122.0 Firefox/122.0

Steps to reproduce:

This will sometimes happen on an individual Reddit post, and I have run into it on other sites. I can get this to happen consistently if I go to metafilter.com and tap on a menu icon on the top of the page, and then tap further down the page.

This is happening in stock Firefox for Android and in Nightly.

Actual results:

The tap brings the pull-to-refresh icon down to where you tapped, and will initiate the refresh if you don't slide the icon back up off the top of the screen.

Expected results:

Whatever else you were intending to tap for - a link, text selection, entering a text box, the beginning of a scroll gesture, etc.

The severity field is not set for this bug.
:tthibaud, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(tthibaud)

I'm wondering if this may be related to this bug as I am seeing that behavior as well, and I could imagine that the way the page "jumps" in that bug could be registered as a pull-to-refresh.

Blocks: 1807071
Flags: needinfo?(tthibaud)

Hey :shardina, thanks a lot for this bug report!
Could you try to update Firefox to 122.1.0, and check if the bug is still reproducible? 

It may have been already fixed by recent patches. In case it is still reproducible on Firefox, would you mind dowloading Firefox Nightly and check the same thing there?

Flags: needinfo?(shardina)

This does still happen in 122.1.0, but so far does appear to be fixed in Nightly!

Flags: needinfo?(shardina)

Thanks a lof for checking!
The patches that fix this bug should reach release next week. If they happen again after you get Firefox 123, can you please comment on this bug?
Until then, I'll mark it as fixed (duplicate of Bug 1872170).

Status: UNCONFIRMED → RESOLVED
Closed: 7 months ago
Duplicate of bug: 1872170
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.