fix(browser): scale iframe for non ui case

[hi-ogawa]

Description

• closes Browser viewport does not match iframe viewport when the UI is disabled #6485

The test case I added is failing on webdriverio regardless of with or without UI. I couldn't figure out webdriverio, so this PR only fixes playwright where it has inconsistency with or without UI.

todo

• playwirhgt
  • works except macos chromium
• preview provider
  • works
• webdriverio provider (keep as is for now)
  • scaling breaks interaction API. It's also reproducible with UI (it might be same as Amazing new locators in 2.1 beta don't seem to work with the interactivity API #6449). This should be fixed first separately.
  • this could be an upstream issue [🐛 Bug]: UI event doesn't work properly inside iframe scaled via css transform webdriverio/webdriverio#13724

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[sheremet-va]

This doesn't fix it when you call page.viewport

We already experimented with this before. Now we just need to keep the same iframe scaling that we have in ui

[hi-ogawa]

This doesn't fix it when you call page.viewport

Ah, I didn't think about that. I've read #6257 and scaling seems more involved but I'll see what I can do.

[netlify]

✅ Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	a82ae78
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/67107c43b2c76d000827d8c0
😎 Deploy Preview	https://deploy-preview-6512--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[hi-ogawa]

Only Mac chromium playwright is timing out with specs/runner.test.ts https://github.com/vitest-dev/vitest/actions/runs/10915841527/job/30296283296?pr=6512#step:9:24

I cannot reproduce it locally on my Linux chromium headless, so it's hard to diagnose what's wrong. I would appreciate if someone can check it on Mac machine locally.

[pkg-pr-new]

@vitest/coverage-istanbul

pnpm add https://pkg.pr.new/@vitest/coverage-istanbul@6512

@vitest/coverage-v8

pnpm add https://pkg.pr.new/@vitest/coverage-v8@6512

@vitest/expect

pnpm add https://pkg.pr.new/@vitest/expect@6512

@vitest/pretty-format

pnpm add https://pkg.pr.new/@vitest/pretty-format@6512

@vitest/mocker

pnpm add https://pkg.pr.new/@vitest/mocker@6512

@vitest/spy

pnpm add https://pkg.pr.new/@vitest/spy@6512

@vitest/snapshot

pnpm add https://pkg.pr.new/@vitest/snapshot@6512

@vitest/runner

pnpm add https://pkg.pr.new/@vitest/runner@6512

@vitest/utils

pnpm add https://pkg.pr.new/@vitest/utils@6512

@vitest/ui

pnpm add https://pkg.pr.new/@vitest/ui@6512

vite-node

pnpm add https://pkg.pr.new/vite-node@6512

@vitest/web-worker

pnpm add https://pkg.pr.new/@vitest/web-worker@6512

@vitest/ws-client

pnpm add https://pkg.pr.new/@vitest/ws-client@6512

vitest

pnpm add https://pkg.pr.new/vitest@6512

@vitest/browser

pnpm add https://pkg.pr.new/@vitest/browser@6512

commit: a82ae78

[hi-ogawa]

@sheremet-va I did some CI debugging, but couldn't figure out mac chromium fail. The CI log suggests test/browser/test/... hangs somewhere and it might be reproduced locally with headless or non ui. Can you try this on your PC?

# or --browser.ui=false
pnpm -C test/browser test-fixtures --browser.headless=true