Dmitry Gozman

> I've also tried to provide a timeout option for my fixture, but it does not help This is an interesting idea! Having a separate timeout would resolve concerns about...

@vitalets We have discussed this issue with the team, and think we should push back. We recommend explaining users that have fixtures timing out in teardown that it's not considered...

@NoamGaash I spent some time on the issue, and the fix is not that straightforward. Therefore, I went ahead and prepared a PR myself - https://github.com/microsoft/playwright/pull/30769. Thank you for the...

@NoamGaash There is a difference between normal operation worker stop, and the case where something went wrong. So my change assumes that during normal worker stop, triggered by `_isWorkerRedundant` or...

@Xinran-Ma This is indeed surprising. Unfortunately, we won't be able to help unless you share a repro with us, so that we can run it locally.

> How about expose the [Input.dispatchTouchEvent](https://chromedevtools.github.io/devtools-protocol/tot/Input/#method-dispatchTouchEvent) ? For example, add a `page.touchscreen.touch()` therefore we could create the `swipe` wrapper by ourselves. I am not really sure what you mean by...

@PupilTong Thank you for the answers! If you believe that developers can implement `swipe()` based on exposed `dispatchTouchEvent` in Firefox, then you should be able to do the same. Therefore,...

Thank you for the issue! I have filed an upstream chromium bug here: https://issues.chromium.org/issues/338414704. We'll see what can be done for the next release.

The fix is available in the recent Chromium, https://github.com/microsoft/playwright/pull/30937 enables it. However, it will have to wait until stable channels pick it up.

@cgatl Thank you for the issue, I can repro.