bug: page.setContent() started failing with timeout errors after upgrading @playwright/test to ~1.56.0

[tomwayson]

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already report this problem, without success.

Stencil Playwright Version

0.2.3

Current Behavior

After upgrading @playwright/test from ~1.55.0 to ~1.56.0, all of our tests that use page.setContent() started failing. The tests that use page.goTo() still work.

Expected Behavior

Tests that use page.setContent() continue to work after upgrading @playwright/test

Steps to Reproduce

I don't have time to create a repro, so I don't expect you to investigate. My hope in sharing this is in case others have the same problem at least they can find this issue and comment. If I have a chance later, I'll create a repro.

Code Reproduction URL

n/a

Additional Information

No response

[EliHeindel]

Our workaround was to override the browser-facing URL in the Playwright config instead of letting @stencil/playwright 0.2.3 derive it from Stencil’s default 0.0.0.0 dev server address.

On our side, page.goto() tests still worked, but tests using page.setContent() started failing after the Playwright bump. Once we set the Playwright baseURL and webServer.url explicitly to http://localhost:3333, those setContent() tests started passing again.

So this looks like @stencil/playwright 0.2.3 is using the Stencil bind address as the browser-facing URL, and localhost works where 0.0.0.0 does not.