fix(web): retain CDP scope and request identity during session preparation (#13188)

This commit is contained in:
morluto authored and GitHub committed 2026-11-21 19:05:13 +00:00
1 parent 56838a036c
commit 5c390198f7
4 files changed
+147 -161

No files matched your search

+11 -8
View File
@@ -423,14 +423,17 @@ main frame.
The web-session timeline uses CDP monotonic seconds where the event producer
provides a comparable timestamp; absent or invalid timestamps are `null` rather
than a synthetic zero. Events buffered while REA samples the window boundary are
retained only when their timestamp places them after that boundary; older events
are excluded. A buffered event without a comparable timestamp may remain as
contextual evidence with `timestamp: null`, accompanied by a limitation stating
that it does not establish activity in the selected window. Main-frame scope
enforcement still applies to contextual navigation events. Network redirect
events retain their paired prior-hop response context when the timestamped
next-request event falls inside the window. Every redirect row, and only a redirect row, has a
than a synthetic zero. After enabling the Page domain, REA buffers timeline
events through preparation and clock sampling. Timestamped rows describe
events after the sampled boundary; earlier requests can still identify a
document load failure that occurs inside the window. A buffered event without a
comparable timestamp may remain as contextual evidence with `timestamp: null`,
accompanied by a limitation stating that it does not establish activity in the
selected window. Main-frame scope enforcement still applies to contextual
navigation events.
Network redirect events retain their paired prior-hop response context when the
timestamped next-request event falls inside the window. Every redirect row, and only a redirect row, has a
`redirect_response` that contains the prior response `url`, CDP-reported `status`,
and `scope`. The URL has transport credentials removed; URL and status are
withheld unless its origin is approved. Missing or malformed response URLs have