Open Bug 1825348 Opened 1 year ago Updated 3 days ago

Touch often fails on firefox android, especially on 3 dot buttons and hamburger menus

Categories

(Fenix :: Browser Engine, defect, P5)

Firefox 113
All
Android

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: weorpq0h4, Unassigned, NeedInfo)

Details

(Whiteboard: [qa-triaged] )

Attachments

(7 files)

Steps to reproduce:

  1. Visit https://www.flipkart.com (alternatively, can be reproduced on amazon or google as well)
  2. Tap on the hamburger menu, or
  3. Search for any product and try to go back by tapping on the arrow near the website's searchbar.

Another way to replicate this touch issue without visiting any website is:

  1. visit about:config on either firefox beta or nighty.
  2. Type anything on the about config searchbar.
  3. Try to clear all by tapping on the x on the right side.
  4. The same thing happens even there.

Actual results:

On the screen recording provided, the left menu didn't show up on multiple occasion. This happens on other websites like amazon.in, github, google and more as well

Expected results:

Websites/firefox should register every single tap like it does on any chromium browser. This is severely ruining the browsing experience for users given how it is not a one off thing and happens not only on websites but even firefox's own elements like about:config and 3 dot button.

For size reasons, screen recording couldn't be shared directly and the video link hid behind a txt file, so here's the direct video link displaying the issue on a website: https://imgur.com/a/WFDM3i9 and here's a link displaying the issue on about:config: https://imgur.com/a/ljf4Gs5

Attachment #9325766 - Attachment mime type: video/mp4 → application/octet-stream

a comparison of touch sensitive area of chrome and Firefox: https://imgur.com/a/PKgj0Sa.

The touch sensitive area for firefox seems to be skewed towards right side maybe. As you can see that on Firefox, taps on top left had no response while taps barely touching bottom right of the menu got perfect response.

Change Request: --- → emergency

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

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Flags: needinfo?(cpeterson)

Thank you for the report!

I was not able to reproduce this issue on the latest Nightly 118.0a1 from 8/22 or Beta 117.0b9. I also tried to reproduce it on Beta 113.0b3
Tested with Motorola Moto G9 plus (Android 11), and Google Pixel 7 PR0 (Android 14).

Could you please provide us with additional details:
Which device did use when encountering this issue?
Could you try to reproduce this issue on the most recent nightly build?

Status: UNCONFIRMED → RESOLVED
Closed: 10 months ago
Flags: needinfo?(weorpq0h4)
Resolution: --- → WONTFIX
Whiteboard: [qa-triaged]

(In reply to Adina Petridean from comment #6)

Could you please provide us with additional details:
Which device did use when encountering this issue?
Could you try to reproduce this issue on the most recent nightly build?

My device is Realme 3 Pro (Android 11)

And yes, I can still reproduce this issue on my latest nightly version 118.0a1 from August 22. Here's a video recording: https://imgur.com/a/ZWTpMcK

Flags: needinfo?(weorpq0h4)
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WONTFIX → ---

Today, I tested this issue on the latest nightly version, 118.0a1 from August 23, and on Beta 117.0b9 using RealMe GT Master Edition (Android 12). The outcome remains the same, I am unable to reproduce it.

(In reply to Adina Petridean from comment #8)

Today, I tested this issue on the latest nightly version, 118.0a1 from August 23, and on Beta 117.0b9 using RealMe GT Master Edition (Android 12). The outcome remains the same, I am unable to reproduce it.

Which website did you test, and please share a screen recording.

Status: REOPENED → UNCONFIRMED
Ever confirmed: false

(In reply to weorpq0h4 from comment #9)

(In reply to Adina Petridean from comment #8)

Today, I tested this issue on the latest nightly version, 118.0a1 from August 23, and on Beta 117.0b9 using RealMe GT Master Edition (Android 12). The outcome remains the same, I am unable to reproduce it.

Which website did you test, and please share a screen recording.

@weorpq0h4 please check the attached files! The video is made with the latest nightly 118.0a1 from 24.08.2023.

Flags: needinfo?(weorpq0h4)

(In reply to Adina Petridean from comment #10)

(In reply to weorpq0h4 from comment #9)

(In reply to Adina Petridean from comment #8)

Today, I tested this issue on the latest nightly version, 118.0a1 from August 23, and on Beta 117.0b9 using RealMe GT Master Edition (Android 12). The outcome remains the same, I am unable to reproduce it.

Which website did you test, and please share a screen recording.

@weorpq0h4 please check the attached files!

I'm not seeing any attached files from you.

Flags: needinfo?(weorpq0h4)
Attached video Rec2.mov

(In reply to Adina Petridean from comment #10)

(In reply to weorpq0h4 from comment #9)

(In reply to Adina Petridean from comment #8)

Today, I tested this issue on the latest nightly version, 118.0a1 from August 23, and on Beta 117.0b9 using RealMe GT Master Edition (Android 12). The outcome remains the same, I am unable to reproduce it.

Which website did you test, and please share a screen recording.

@weorpq0h4 please check the attached files!

Okay, I've seen your screen recording. To actually reproduce the issue, you'll need to tap on the left corner of the hamburger menu, NOT the center or the right corner. To get a better idea, you can watch this: https://imgur.com/a/ZWTpMcK

Attached video Rec1-1.mov

(In reply to Adina Petridean from comment #10)

Could you take a look at my comment #4 https://bugzilla.mozilla.org/show_bug.cgi?id=1825348#c4 I have explained the issue a bit better there because the main issue that I've encountered so far on multiples issues is with the lack of touch response on left side primarily.

I'll attach a new video now with Motorola Moto G9 plus (Android 11) and later with RealMe GT Master Edition (Android 12).

Attached video Rec3.mp4

(In reply to Adina Petridean from comment #16)

I'll attach a new video no with Motorola Moto G9 plus (Android 11) and later with RealMe GT Master Edition (Android 12).

Trying to explain this again with 2 videos that I just tried on Nightly 118.a01 from 24th August and Google Chrome:

If you take a look at this video: https://imgur.com/a/7bm6R9o, you'll see that the taps on left corner are perfectly recognized by the Chrome Browser.

Whereas the taps on left corner are not recognized by Firefox: https://imgur.com/a/HSqTJ01

Please, when you try to reproduce the issue next time, tap on the left corner and not on the middle or right corner. Let me know, thanks.

Thank you for your patience. On both the Motorola Moto G9 Plus (Android 11) and the Google Pixel 7 Pro (Android 14), I can't reproduce this issue no matter which hamburger corner I tap (new recording attached).

Attached video rec4.mp4

(In reply to Adina Petridean from comment #19)

Thank you for your patience. On both the Motorola Moto G9 Plus (Android 11) and the Google Pixel 7 Pro (Android 14), I can't reproduce this issue no matter which hamburger corner I tap (new recording attached).

Thanks to you too for the quick followups.

(In reply to weorpq0h4 from comment #21)

(In reply to Adina Petridean from comment #19)

Thank you for your patience. On both the Motorola Moto G9 Plus (Android 11) and the Google Pixel 7 Pro (Android 14), I can't reproduce this issue no matter which hamburger corner I tap (new recording attached).

Thanks to you too for the quick followups.

I'll try later with the RealMe GT Master Edition (Android 12) device and will provide a video afterwards.

@weorpq0h4 please check the new video made with RealMe GT Master Edition (Android 12) device.

Attached video rec5.mov
Severity: -- → S4
Priority: -- → P5

Thank you for the report!

I tested with today's Nightly build 128.0a1 from 5/24 with Realme GT Master Edition (Android 13), and Xiaomi Mi8 Lite (Android 10), and was unable to reproduce the issue.
Could you retest with the latest Firefox for Android builds, and let us know if this is till reproducible to you?

Flags: needinfo?(weorpq0h4)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:boek, since the bug has recent activity, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(weorpq0h4) → needinfo?(jboek)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: