Default mock for the window.print call in browser mode

[charlieforward9]

Clear and concise description of the problem

I see there are default mocks for the window.confirm, window.alert, etc... calls but nothing for print.

Given this open, unaddressed and seemingly un-workaroundable issue: #7290 (and the linked issues within), I cannot mock my reactToPrint module within my tests, so the print window pops up, and on my CI tests, it hangs the runner. Ive tried to mock the print call myself, but cant seem to get it right.

Suggested solution

Add a default mock for the window.print call:

https://github.com/vitest-dev/vitest/blob/main/packages/browser/src/client/tester/dialog.ts#L21-L25

(i think)

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[hi-ogawa]

I think we can include window.print there. PR welcome 👍

Ive tried to mock the print call myself, but cant seem to get it right.

It should be possible by simply patching a global or https://vitest.dev/guide/mocking.html#globals. If that's not working, then the issue could be somewhere else (like how reactToPrint uses it). Can you prepare reproduction just in case? (so you can also confirm the fix actually works for you).

[charlieforward9]

From MatthewHerbst/react-to-print#782, I now understand that we do not use window.print() directly, so this PR will not help me like I thought it would.

While I'd be honored to attain contributor status in this repo, I must prioritize the release our our app right now - being a team of 2 is tough...

Please feel free to assign me to this so I can find it easier in my backlog when my time frees up. Thanks!