Closed Bug 1847541 Opened 2 years ago Closed 2 years ago

The burger menu fails to open after navigating on the page at reddit.com

Categories

(Core :: JavaScript Engine, defect, P3)

Firefox 118
Other
Android
defect

Tracking

()

RESOLVED DUPLICATE of bug 1847813
118 Branch
Tracking Status
firefox116 --- unaffected
firefox117 --- unaffected
firefox118 + fixed

People

(Reporter: rbucata, Unassigned)

References

()

Details

(Keywords: regression)

Attachments

(1 file)

Attached image Screenshot_7.png

Environment:
Operating system: Android 12
Firefox version:Firefox Nightly 118.0a1 (2015966755-🦎118.0a1-20230805212033🦎)

Preconditions:
Clean profile

Steps to reproduce:

  1. Navigate to: https://www.reddit.com
  2. Tap on the burger menu.
  3. Tap on any option presented.
  4. From the newly opened page, tap on the back button of the browser/device.
  5. Tap on the burger menu again.
  6. Observe the result.

Expected Behavior:
The burger menu opens.

Actual Behavior:
The burger menu does not open.

Notes:

  • Reproducible regardless of the status of ETP.
  • Reproducible on the latest build of Firefox Nightly , also when opening a post.
  • Works as expected using Chrome and Firefox Release.
  • Reproducible 5/10 times and on other items located in the top menu bar(e.g "Search bar").
  • The "Topics" section fails to load when the menu works.
  • Screenshot attached.
  • Issue found during WebCompat team [Top100] websites testing.
See Also: → 1847702

:Raul Bucata do you know if 117 is also affected and do you have a regression window?

Flags: needinfo?(rbucata)

Hi Donal. On the latest Nightly, I can not reproduce the burger menu not responding following the above steps to reproduce, just the "Topics" section not loading, 5/10 times on the first access of the page, without following the steps to reproduce. On the latest Beta, I can not reproduce both the burger menu not responding or the "Topics" section not responding. I have a feeling that this might be related to: https://bugzilla.mozilla.org/show_bug.cgi?id=1847702. I can also amend the report to better reflect the current situation since at the time it was reported, the behaviour was different.

Tested with:

Browser / Version: Firefox Release 116.0 (2015964771-🦎116.0-20230727152340🦎)/ Firefox Nightly 118.0a1 (2015967139-🦎118.0a1-20230807215239🦎)/ Firefox Beta 117.0b5 (2015967131-🦎117.0-20230808215502)🦎)
Operating System: Samsung A51 (Android 11) -1080 × 2400 pixels 20:9 aspect ratio (~405 ppi density)
Operating System: Google Pixel 3 (Android 12) -1080 x 2160 pixels, 18:9 ratio (~443 ppi density)

Flags: needinfo?(rbucata)
Flags: needinfo?(dmeehan)

I was able to reproduce this in 118 nighty but not in 117 beta
regressionwindow-wanted to track this down

Flags: needinfo?(dmeehan)
Whiteboard: [qa-regression-triage]

I was unable to repro this in the latest build of Fenix nightly. Possibly this was the same root cause as Bug 1847813.
:Raul Bucata Could you confirm this is no longer repro for you also?

Flags: needinfo?(rbucata)
See Also: → 1847813

I was not able to reproduce the issue anymore.

Tested with:

Browser / Version: Firefox Nightly 118.0a1 (2015968675-🦎118.0a1-20230816094547🦎)
Operating System: Samsung A51 (Android 11) -1080 × 2400 pixels 20:9 aspect ratio (~405 ppi density)
Operating System: Google Pixel 3 (Android 12) -1080 x 2160 pixels, 18:9 ratio (~443 ppi density)

Flags: needinfo?(rbucata)
Status: NEW → RESOLVED
Closed: 2 years ago
Component: Mobile → JavaScript Engine
Duplicate of bug: 1847813
Product: Web Compatibility → Core
Resolution: --- → DUPLICATE
Target Milestone: --- → 118 Branch
See Also: 1847813
Whiteboard: [qa-regression-triage]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: