Skip to content

Testing on Safari requires user intervention to proceed #1253

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
lucacasonato opened this issue Jun 6, 2020 · 1 comment
Open

Testing on Safari requires user intervention to proceed #1253

lucacasonato opened this issue Jun 6, 2020 · 1 comment

Comments

@lucacasonato
Copy link

lucacasonato commented Jun 6, 2020 •
edited
Loading

In Catalina opening a file in Safari requires the user to confirm that they want to open the file in the Safari UI. Because of this testing on safari does not work anymore without manual user interaction. According to my research this has been broken since at least Mojave.
@lucacasonato lucacasonato mentioned this issue Jun 6, 2020
Open
@grouma
Copy link
Member

grouma commented Jun 8, 2020

You are correct as I verified this is an issue on Mojave. A quick Google search shows other testing frameworks also have this issue:
testem/testem#1387

There is a possible workaround:

I have ran into this as well with Github Actions VMs and locally as well. There's something for Karma via AppleScript to workaround this. https://github.com/brandonocasey/karma-safari-applescript-launcher.

That being said I don't think this is something we will make progress on in the near term.

@grouma grouma changed the title Testing on Safari is not working in Catalina Testing on Safari requires user intervention to proceed Jun 8, 2020
@Ne0n11 Ne0n11 mentioned this issue Mar 21, 2024
Closed
@natebosch natebosch mentioned this issue Sep 10, 2024
Merged
natebosch added a commit that referenced this issue Sep 11, 2024
@natebosch
Run package:test tests on mac (#2280)
9a2d155 
This will exercise things like launching browsers (where they are
currently working on CI).

Add `osx` to the sharded `package:test` tests alongside `windows`. These
exercise the majority of OS specific behavior.

Skip existing safari tests due to a bug running tests in non-interactive
environments. (#1253)

Skip existing firefox tests due to a changed executable path. (Planned
fix in #2276)

Refactor a ternary chain to an if/else chain to add the extra
conditions for firefox and safari.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@grouma @lucacasonato