@userquin I would also love to have https://github.com/user-attachments/assets/29e796ae-6c84-4cf7-8328-b846e3df1f35 in "Running Tests" section - could you help me with that? (need dark mode)

check this 2 dead links: https://app.netlify.com/sites/vitest-dev/deploys/66ab9d78d3068b00084d4d00#L358-L359

check this 2 dead links: app.netlify.com/sites/vitest-dev/deploys/66ab9d78d3068b00084d4d00

Fixed just now

✅ Deploy Preview for vitest-dev ready!

Name	Link
🔨 Latest commit	2209d3c
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/66b09853b726730008e13698
😎 Deploy Preview	https://deploy-preview-6257--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.

So, now the only way to access the browser mode page is from the navbar, maybe we can add the link in the left aside. On mobile the browser mode link will be on top right menu and missing from the left menu hamburger button.

(just add the Browser Mode link without expandable children)

So, now the only way to access the browser mode page is from the navbar, maybe we can add the link in the left aside. On mobile the browser mode link will be on top right menu and missing from the left menu hamburger button.

(just add the Browser Mode link without expandable children)

My logic was that it is still displayed in the right hamburger on mobile. Isn't it enough?

It is fine, no other entries in the navbar present.

FYI: maybe we can remove mastodon, X and discord links from resources navbar menu, already present in the navbar

@userquin @JessicaSachs made iframe scalable (similarly to how cypress implements it) - please check when you have time 🙏🏻

Note: I didn't change the viewport reset yet, it's a bit tricky (it won't be changed in this PR)

Oof, I forgot about the "Select a test to run" use case 👀

Oof, I forgot about the "Select a test to run" use case

from the ui?

The ui doesn't start, Vitest hangs when running nr test:browser:preview or any other provider.

I searched the rationale for the decision to make the iframe scaled, but I didn't find any explanation, except for the comment above saying that "Cypress did it". #6257 (comment)

When I'm trying to make visual tests and save snapshots/screenshots, they also appear scaled because of this.
The visual tests should never be scaled (imho).
At least, Vitest could add an option to disable scaling or forcing some custom factor.