Closed Bug 1991855 Opened 24 days ago Closed 9 days ago

Google Meet is broken with Navigation API enabled

Categories

(Core :: DOM: Navigation, defect)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1993431
Tracking Status
firefox145 --- affected

People

(Reporter: zcorpan, Unassigned)

References

(Blocks 1 open bug)

Details

STR:

  1. Ensure the preference dom.navigation.webidl.enabled is enabled
  2. Join a meeting at https://meet.google.com
  3. Click the video settings button next to the camera toggle.
  4. Click the settings button.
  5. Close the settings dialog.

Expected results
The dialog is closed.

Actual results
You leave the meeting (and the dialog is closed).

It works for me, with Nightly 145.0a1 (2025-09-30), on Win11.

I can reproduce with Nightly 145.0a1 (2025-10-01) on Ubuntu 24

Severity: -- → S3

(In reply to Hsin-Yi Tsai (she/her) [:hsinyi] from comment #1)

It works for me, with Nightly 145.0a1 (2025-09-30), on Win11.

Updated - I saw the problem as well.

Closing dialog has nothing specific to do with the bug - it just navigates back. The back-navigation itself has a problem.

  1. Open any modal popup - like step 3 of comment #0 (but many other ways to do so)
  2. You see the new history item is created.
  3. Navigate back from the browser chrome

Expected: Back-navigation should only close the popup, as Chrome does
Actual: It causes actual full page navigation.

And the history item is added by the traditonal history.pushState(). Does enabling Navigation API do anything special with the existing History API?

nsGlobalWindowInner::DispatchSyncPopState is called but only after the navigation happened. Something is causing navigation earlier.

This is potentially just bug 1993239? Google Meets certainly subscribes beforeunload.

Status: NEW → RESOLVED
Closed: 9 days ago
Duplicate of bug: 1993431
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.