Thanks for your review!

It seems that it's not just firefox that has the problem.

Although only changing firefox can solve these two issues, the three browsers have not been able to pass the test completely before.

Firefox, webkit, and chrome are all inconsistent for javascript|text/html frame loading events.

And it looks like not waiting for non-url frames has little effect on behavior, so I went with this solution.

Hello, can I download the latest package to solve this problem, or change my case according to your code

This pr has not been merged yet.

You can cherry-pick and build it yourself.

Or modify the files in node_module.

@liuxingbaoyu thank you for the PR and awesome tests.

So indeed each browser struggles differently. Here's the summary:

• javascript-src iframe
  • chromium: ❌ never fires "networkidle" for iframe
  • webkit: ✅
  • firefox: ❌ never fires "load" and "networkidle" for iframe
• data-src iframe
  • chromium: ✅
  • webkit: ❌ never fires "networkidle" for iframe
  • firefox: ❌ never fires "networkidle" for iframe
• blob-src iframe
  • chromium: ❌ never fires "networkidle" and "load" for iframe
  • webkit: ✅
  • firefox: ❌ never fires "domcontentloaded", "load" and "networkidle" for iframe

Let me see if it's worth fixing upstream in browsers or on our side.

This pr has not been merged yet.

You can cherry-pick and build it yourself.

Or modify the files in node_module.
Excuse me, how can I modify node_ Module file, which package needs to be modified

This pr has not been merged yet.

You can cherry-pick and build it yourself.

Or modify the files in node_module.

My node_module There is no playwright-core package in the module file

After changing according to your idea, my original case can't run. Have you encountered this problem

Most of these issues have been fixed, thank you for the PR!