Ross Wollman

@JonWallsten Thanks! Where possible, please paste the contents of files instead of screenshots. I'll review tomorrow again once you've had a chance to structure the suggestions/pointers. Having something I can...

Thanks for your report! If you need logs, using the [environment variable](https://github.com/microsoft/playwright/issues/16485) or [Logger API](https://playwright.dev/docs/api/class-logger) are the correct ways of doing it. To my knowledge: ```ts import debug from 'debug';...

I can repro. Even with a logger like: ``` const browser = await playwright.chromium.launch({ logger: { isEnabled: () => true, log: (name, severity, message, args) => console.log(name, severity, message, args),...

> I tried process.env.DEBUG="pw:*" from the test.js script, and that did not work. Maybe because of how Mocha works? I'm assuming your script imports/requires mocha at the top of your...

> I saw your suggestion, but I can't figure out how to get Mocha to work with an inline import using import('mocha').then(...). Let me know if you know how to...

Does the following work? ``` const mocha = await import('mocha'); ``` Again, just a workaround until a more info is plumbed through the logger.

> Any chance the extra logger info will make it into 1.27? There are no plans at the moment. (When we have an idea of a release milestone, we tag...

Thanks for the report — there is indeed an issue with the debug experience here, and I can repro manually! Opening the inspector does appear to break things, so we'll...

I downgraded to `1.25.2` and the issue still happens, so this does not look like a 1.26 regression at the moment. Does that match your experience? Did this workflow used...

This turns out to be an upstream bug in WebKit — its inspector does not support multiple connections (e.g. Playwright and the WebKit Inspector UI). Adding 1.27 so we can...