Skip to content

Conversation

@burg
Copy link

@burg burg commented Dec 10, 2025

This is a draft and will be revised prior to pushing to prod.

(removed unhelpful commit template for now)

Second editing session adds more details about Target system.
@burg burg force-pushed the eng/bburg/1209-inspector-site-isolation branch from 4adf9cc to 4842b9a Compare December 11, 2025 05:15

## What are the main changes are being proposed?

- [X] Add new `Frame` target type which represents a place that commands can be targeted at. A Page target has one or more Frame targets.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A Page target has one or more Frame targets.

I don't think it's accurate to say this, as there's no hierarchy between the targets, unlike in DOM. We don't mean to let Page targets "own" Frame targets, and we certainly don't plan to expose the remote pages as Page targets to own its Frames. The Page and Frame targets' co-existence is merely a consequence of the slow transition, and our plan is to remove Page targets altogether

Unless you meant "A WebPage target has one or more Frame targets", which I wouldn't consider precise either—the WebPage target reports creation and deletion of Frame targets, not own them, correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants