-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Static badge Make Badge
button always disabled on Safari
#7324
Comments
Make Badge
button always disabled on SafariMake Badge
button always disabled on Safari
This is an issue where it would be great to get a community contribution for the fix, or a bit of time from you @paulmelnikow if nobody steps in. I don't use a mac so can't reproduce/debug this and I'm pretty sure Caleb/P-Y don't use macs either |
Correct, I've no way of testing this. I was curious whether any automated testing (with Cypress or otherwise) would be capable of detecting/confirming/preventing this sort of thing, though I suppose we'd at least need a Mac build/CI environment to test on |
OK. I can give a check. |
My theory is that this issue is caused by sindresorhus/decamelize#36 after upgrading decamelize in #7098 I've submitted a PR over at #7449 to revert decamelize to version 5. I have no way of testing this myself but is someone who has an i-Device of some description able to check the staging deploy at https://shields-staging-pr-7449.herokuapp.com/ and see if that fixes it in Safari? The staging deploy is on a dyno that goes to sleep so it might take a while to load |
@chris48s Sindre already mentioned that. Let's stay on version 3. Both |
New staging deploy up. Can we try this one? |
Are you experiencing an issue with...
shields.io
🐞 Description
Operating system: macOS Monetary
Browser version: Safari 15.1
How to reproduce
Make Badge
Relevant issue
I cannot open
http://localhost:3000
on my local. It always shows the error view. This issue can only be reproduced on Safari.I guess it's agatsby
-related issue.🔗 Link to the badge
No response
💡 Possible Solution
No response
The text was updated successfully, but these errors were encountered: