Closed Bug 1915083 Opened 5 months ago Closed 2 months ago

www.dairyqueen.com - The "Menu" option from the burger menu returns a page stuck in a loading state with ETP set to STRICT

Categories

(Web Compatibility :: Privacy: Site Reports, defect)

ARM
Android
defect

Tracking

(firefox129 affected, firefox131 affected)

RESOLVED WORKSFORME
Tracking Status
firefox129 --- affected
firefox131 --- affected

People

(Reporter: rbucata, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])

Environment:
Operating system: Android 10
Firefox version: Firefox 131.0

Preconditions:
ETP set to STRICT

Steps to reproduce:

  1. Navigate to: https://www.dairyqueen.com
  2. Tap on the burger menu
  3. Once the menu is triggered, tap on the "Menu" option and observe

Expected Behavior:
The page loads

Actual Behavior:
The page is stuck in a loading state

Notes:

  • Reproduces in ETP Strict Mode only
  • Reproduces in Firefox Nightly, and Firefox Release
  • Does not reproduce in Chrome and for other options located inside the burger menu

Created from https://github.com/webcompat/web-bugs/issues/140924

Component: Site Reports → Privacy: Site Reports

It's a bit slow to load the content for https://www.dairyqueen.com/en-us/menu/ but eventually is loads it properly. Tested on Firefox 133.0 release on macOS in ETP "strict".

Could you elaborate what exactly you mean by "burger menu"? A screenshot or screencast would be helpful. If you mean https://www.dairyqueen.com/en-us/menu/ could you check if you can still reproduce the issue?

Flags: needinfo?(rbucata)

It seems to work now for me as well, can not see any difference between ETP STRICT or STANDARD, as the menu page loads. I was referring to the three vertical lines, when tapped on they trigger https://www.dairyqueen.com/en-us/menu/.

Flags: needinfo?(rbucata)

Thanks! I'll close it for now then.

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.