Pavel Feldman

Ah, so you want the user to control both sides of the story, so hooksConfig's schema is left to the user to define? That's fine with me.

The answer to this question is that if we ignore it, we won't be able to replay it. And we'd like to have a good ration of replay-able scenarios recorded...

Archiving this

> If a trace is available, the process will be even more streamlined without the need for video recordings Could you explain how trace is helpful here?

Investigation note: - worker is stopped - graceful worker termination is scheduled concurrently with the worker teardown

Is there a user report for this? If you want to move off wallTime as an action identifier in the trace, we can do that, but that'll be a bigger...

Try replacing ` src="/playwright/index.ts"` with ` src="./index.ts"` to resolve index.ts properly.

That's unfortunate. In this case we need a reduced repro in a form of an archive or a repo that we can clone.

@BrianMar would you be willing to send a PR?

This looks like something you want to bring up with Firefox team. I'm opening that page in FF and see no WS in their network panel.