Bug 248177
| Summary: | browser.tabs.onUpdated() should fire when history.pushState() is used | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Timothy Hatcher <timothy> |
| Component: | WebKit Extensions | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | karlcow, timothy, webkit-bug-importer |
| Priority: | P2 | Keywords: | BrowserCompat, InRadar |
| Version: | WebKit Local Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://github.com/w3c/webextensions/issues/328 | ||
Timothy Hatcher
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |