Pavel Feldman

#### Why was this issue closed? Thank you for your involvement. This issue was closed due to limited engagement (upvotes/activity), lack of recent activity, and insufficient actionability. To maintain a...

#### Why was this issue closed? Thank you for your involvement. This issue was closed due to limited engagement (upvotes/activity), lack of recent activity, and insufficient actionability. To maintain a...

#### Why was this issue closed? Thank you for your contribution to our project. This issue has been closed due to its limited upvotes and recent activity, and insufficient feedback...

#### Why was this issue closed? Thank you for your involvement. This issue was closed due to limited engagement (upvotes/activity), lack of recent activity, and insufficient actionability. To maintain a...

#### Why was this issue closed? Thank you for your contribution to our project. This issue has been closed due to its limited upvotes and recent activity, and insufficient feedback...

@azad-derakhshani-GS > allowing multiple people with different screens to work on testautomation without any problems (fixed viewport would be problematic because everyone has different monitors and resolutions) This looks backwards...

Support for downloads is on the way. It needs changes to Chromium that are under [review](https://chromium-review.googlesource.com/c/590913).

~~@aslushnikov [496577](https://chromium-review.googlesource.com/c/chromium/src/+/590913) landed a week ago, it should be few lines of code on your end.~~ Looks like aslushnikov@ bakes something more upstream to deliver an event upon download.

Could you help me understand why the following notation is not solving this request? ```js condition && await test.step('my step', async () => { ... }); ```

There is no way to attach to Chromium on Android or MobileSafari on iOS. Playwright aims at running on your desktop and in your CI/CD, targeting device farms is outside...