Skip to content

Conversation

@karlseguin
Copy link
Collaborator

exit_when_done is pretty much a sneaky way to get CDP knowledge into the page. exit_when_done == true means "this isn't a CDP session".

extra_socket is another sneaky weay to get CDP knowledge into the page. When we get an extra_socket message it means "Return control to the CDP server".

Therefore it should be impossible to get an extra_socket message (return to CDP) when exit_when_done == true (this isn't a CDP session).

exit_when_done is pretty much a sneaky way to get CDP knowledge into the page.
exit_when_done == true means "this isn't a CDP session".

extra_socket is another sneaky weay to get CDP knowledge into the page. When
we get an `extra_socket` message it means "Return control to the CDP server".

Therefore it should be impossible to get an `extra_socket` message (return to
CDP) when `exit_when_done == true` (this isn't a CDP session).
@krichprollsch krichprollsch merged commit e6b9be5 into main Sep 19, 2025
10 checks passed
@krichprollsch krichprollsch deleted the assert_corretly_set_exit_when_done branch September 19, 2025 10:20
@github-actions github-actions bot locked and limited conversation to collaborators Sep 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants