Bug 248177 - browser.tabs.onUpdated() should fire when history.pushState() is used
Summary: browser.tabs.onUpdated() should fire when history.pushState() is used
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Extensions (show other bugs)
Version: WebKit Local Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: https://github.com/w3c/webextensions/...
Keywords: BrowserCompat, InRadar
Depends on:
Blocks:
 
Reported: 2022-11-21 08:59 PST by Timothy Hatcher
Modified: 2022-11-21 16:08 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Hatcher 2022-11-21 08:59:01 PST 
From https://github.com/w3c/webextensions/issues/328:

1) Open https://example.com.
2) In an extension, add a browser.tabs.onUpdated listener.
3) In the console of the web page, run history.pushState({}, "", "/test").

Currently:

* Chrome fires both a "loading" event and a "completed" one in immediate succession.
* Firefox fires a single "completed" event.
* Safari fires no events.

rdar://84204907