[Webkit-unassigned] [Bug 248177] New: browser.tabs.onUpdated() should fire when history.pushState() is used
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Nov 21 08:59:01 PST 2022
https://bugs.webkit.org/show_bug.cgi?id=248177
Bug ID: 248177
Summary: browser.tabs.onUpdated() should fire when
history.pushState() is used
Product: WebKit
Version: WebKit Local Build
Hardware: Unspecified
URL: https://github.com/w3c/webextensions/issues/328
OS: Unspecified
Status: NEW
Keywords: InRadar
Severity: Normal
Priority: P2
Component: WebKit Extensions
Assignee: webkit-unassigned at lists.webkit.org
Reporter: timothy at apple.com
CC: timothy at apple.com, webkit-bug-importer at group.apple.com
>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
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20221121/7707f115/attachment.htm>
More information about the webkit-unassigned
mailing list