Dmitry Gozman

@Georgegriff Could you please file a separate issue by filling in "Bug Report" template and providing a repro? It could be that your issue is a different one. This will...

@Georgegriff As I said, s separate issue will help us with prioritization. Also, we need some code we can run that reproduces the issue. A short test that sets headers...

I tried the following: ```sh git clone https://github.com/debs-obrien/debbie.codes.git cd debbie.codes npm i npx playwright install npx playwright test --project=chromium --grep="microsoft mvp link in home page works" ``` Somehow it works...

> @dgozman Why is this tagged as collecting-feedback isn't it a bug? It worked well in old versions e. g. 1.26.1. This involves print preview, which is not the top...

We are unable to reproduce this issue, with `playwright v1.27.1/v1.28` and `node v18/v19`. Is there anything else that's special in your setup? Other VSCode extensions? Using `yarn` or some other...

@qasamppa I am not sure we'll be able to help you without any more information from your side. I'd suggest trying to disable other extensions, or playing with VSCode version.

@NVolcz I think we can probably do something like `expect(image1).toMatchImage(image2)` for this usecase. See also #18897. In your particular case, I can recommend to produce screenshots once in `production` environment,...

@ambiguous48 Yes, so far I think that `toMatchImage()` could support both buffers and file paths.

@dimsamaras Could you run your playwright script with `DEBUG=pw:api,pw:protocol` and post the logs here? Since some APIs work, and others do not, the problem is most likely in the protocol...

> grid log says - WARN [ProxyWebsocketsIntoGrid$ForwardingListener.onError] - Error proxying websocket command > java.net.ProtocolException Playwright does indeed use proxying websocket functionality. We'll take a look, but for now I'd suggest...