Open Bug 2024555 Opened 1 month ago Updated 1 month ago

Nullify ongoing navigate event/method tracker on successful cross-document navigation

Categories

(Core :: DOM: Navigation, defect)

Product:
Core
Component:
DOM: Navigation
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: noam.j.rosenthal, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36

Steps to reproduce:

  • navigate to a new document (e.g. using navigate())
  • go back, asserting that BFCache took place
  • Perform a same-document navigation (e.g. history.pushState)

Actual results:

navigateerror was fired, and the original navigate().finished promise rejects, as if the new pushState() aborted the original navigate().

Expected results:

navigatesuccess should fire, and the original navigate().finished promise should hang.

See https://github.com/whatwg/html/pull/12024 and its WPT

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Navigation' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: Navigation
Product: Firefox → Core

...since you commented in the spec issue.

Severity: -- → S3
Flags: needinfo?(afarre)
You need to log in before you can comment on or make changes to this bug.