browser

public/browser

Fork 0

mirror of https://github.com/lightpanda-io/browser.git synced 2026-03-29 08:00:05 +00:00

Commit Graph

Author	SHA1	Message	Date
Karl Seguin	ea422075c7	Remove unused imports And some smaller cleanups.	2026-03-27 12:45:26 +08:00
Pierre Tachoire	40c3f1b618	cdp: fix req id resolver, they are REQ- not RID-	2026-03-04 13:00:16 +01:00
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

Author

SHA1

Message

Date

Karl Seguin

ea422075c7

Remove unused imports

And some smaller cleanups.

2026-03-27 12:45:26 +08:00

Pierre Tachoire

40c3f1b618

cdp: fix req id resolver, they are REQ- not RID-

2026-03-04 13:00:16 +01:00

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

3 Commits