Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 976ef42833709a75648edfb40473b7a6486fd09d
https://github.com/WebKit/WebKit/commit/976ef42833709a75648edfb40473b7a6486fd09d
Author: Yury Semikhatsky <[email protected]>
Date: 2026-10-08 (Thu, 08 Oct 2026)
Changed paths:
A
LayoutTests/http/tests/inspector/target/loader-id-for-cross-site-redirect-expected.txt
A
LayoutTests/http/tests/inspector/target/loader-id-for-cross-site-redirect.html
M Source/WebCore/inspector/InspectorIdentifierRegistry.cpp
Log Message:
-----------
Web Inspector: loaderId changes when a navigation continues in another process
https://bugs.webkit.org/show_bug.cgi?id=326871
Reviewed by Devin Rousso.
With process swap on navigation, one navigation can have document loaders in
several web processes, for
example when a cross-site redirect makes the load continue in a new process.
LegacyIdentifierRegistry gives
each of them its own per-process loader ID, so the Network events from the old
process and the Page and
Network events from the new process cannot be matched.
Derive the loader ID from the navigation ID, which is the same in all processes
that take part in the
navigation, as BackendIdentifierRegistry already does. Keep the per-loader
fallback for loaders without a
navigation ID.
Test: http/tests/inspector/target/loader-id-for-cross-site-redirect.html
*
LayoutTests/http/tests/inspector/target/loader-id-for-cross-site-redirect-expected.txt:
Added.
*
LayoutTests/http/tests/inspector/target/loader-id-for-cross-site-redirect.html:
Added.
* Source/WebCore/inspector/InspectorIdentifierRegistry.cpp:
(Inspector::LegacyIdentifierRegistry::loaderId):
Canonical link: https://commits.webkit.org/323167@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
