Karl Seguin e2a1ce623c Rework CDP frameIds (and loaderIds and requestIds and interceptorIds) ...

Our BrowsingContext currently supports 1 target. So we have a per-BC target_id.
Previously, our target had 1 "frame" - our page. So we often treated the
targetId as the frameId. But to work with frames, we need page-specific
frameIds and loaderIds.

This tries to clean up our ids (a little). frameIds are now ids derived from
a new incrementing page.id. This page.id has to be passed around (via http
Requests and through notifications) in order to properly generate messages with
a frameId.

2026-02-19 13:01:41 +08:00

2.4 KiB

Raw Blame History

View Raw