Dmitry Gozman

Thanks for the archive! I did play with it, but failed to reproduce the issue so far. In the included traces I don't see the popup dialog at all, am...

@eatonjl I played with it more, following your instructions. Unfortunately, I was not able to repro the blank popup - perhaps it's racy enough to not repro on my computer....

@eatonjl Fix for the `childFrames` issue depends on a larger refactoring in Firefox code, so no precise ETA yet, unfortunately.

@maranbalu We have updated [the docs](https://playwright.dev/java/docs/next/selenium-grid) - perhaps you could follow them to resolve your issue?

Closing as per above. If the problem persists and you have a repro, please file a new issue and link to this one.

@JonWallsten Thank you for the PR! Before we proceed, I'd like to clarify a few things: 1. Looking at the repro, it seems like you are running playwright with `ts-node`:...

@JonWallsten You should stop passing `TS_NODE_PROJECT` environment variable. As I said, it unfortunately confuses our tsconfig loader, and we'll remove it from future releases. If you do that, tsconfig should...

@JonWallsten We would like to understand the scenario to make an informed decision. If you have a usecase that does not work, we would be happy to help you! In...

@JonWallsten If I understood you correctly, you want paths from `tsconfig.json` to apply when `require`'ing from a compiled `.js` file? This is not something Playwright supports, because it assumes that...

I discussed this issue with the team and we arrived to the following: - Removing TS_NODE_XXX env variables support, because we are not following `ts-node` semantics. - Do not respect...