-
Notifications
You must be signed in to change notification settings - Fork 61
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.
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
localhost fails on OS X Sonoma / Safari 17 #263
Comments
Krinkle
added a commit
to qunitjs/browserstack-runner
that referenced
this issue
May 29, 2024
Krinkle
added a commit
to qunitjs/qunit
that referenced
this issue
May 29, 2024
This should address the intermittent timeout we see with Safari 17 on macOS Sonoma. Ref browserstack/browserstack-runner#263.
Krinkle
added a commit
to qunitjs/qunit
that referenced
this issue
May 29, 2024
This should address the intermittent timeout we see with Safari 17 on macOS Sonoma. Ref browserstack/browserstack-runner#263.
Krinkle
added a commit
to qunitjs/qunit
that referenced
this issue
May 29, 2024
This should address the intermittent timeout we see with Safari 17 on macOS Sonoma. Ref browserstack/browserstack-runner#263.
Krinkle
added a commit
to qunitjs/qunit
that referenced
this issue
May 29, 2024
This should address the intermittent timeout we see with Safari 17 on macOS Sonoma. Ref browserstack/browserstack-runner#263.
Yes this is expected, due to security restrictions in Safari, we would need to use the URL as bs-local instead of localhost |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm experiencing intermittent failures where tests on OS X Sonoma with Safari 17.3 fail after a 10 minute timeout.
By logging into the BrowserStack Automate panel during, and using "Start interactive session" to understand what was happening, I noticed that it said
Clicking on the address bar and changing the hostname to
bs-local.com:8899
showed a passing test. So it seems whatever has been affecting iOS is now affecting macOS as well?The text was updated successfully, but these errors were encountered: