Holger Benl

Could you check if using `"firefoxExecutable": "stable"` or `"firefoxExecutable": "nightly"` makes any difference?

Sorry, I can't figure out what's going on here. I've added a few logs in the latest release (2.14.1) that may give me a clue, so you could try with...

Done. I'll keep the extension up-to-date on open-vsx.org in the future.

This is working for me when I add `export BIDI_FFPATH="/Applications/Firefox Nightly.app/Contents/MacOS/firefox"` to my `~/.zprofile` and follow the steps in this issue's description.

> [@yury-s](https://github.com/yury-s) would it be possible for the extension to support such a custom debugger configuration? We were thinking of [something like this](https://marketplace.visualstudio.com/items?itemName=hbenl.vscode-mocha-test-adapter#custom-debugger-configuration). In this configuration we could set `autoAttachChildProcesses`...

I think the "default" value should also be exposed in the Playwright API (#36877).

FWIW I think it's wrong that Playwright Firefox and Safari currently report cookies with an unspecified `SameSite` attribute to have `SameSite=None`. This is [expected behavior according to the tests](https://github.com/microsoft/playwright/blob/990f576c9106939171d22801bad44438e38a26fc/tests/config/browserTest.ts#L76-L87) but...

This could be caused by a bug that I just fixed in version 2.13.0. Could you retry with that version?

Which version of Firefox do you use? I've noticed a [bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1941027) in the current Developer and Nightly editions that could cause this. If you've used one of those, try with...

OK, so this is a different issue. Could you share your `logs/ffdebug.log`?