-
-
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
Github blocks all SVGs in all readmes #112
Comments
SVG caching is disabled at the moment; it'll be coming back. |
If it helps, the above email was from @atmos |
@holman Good to know. On that topic, could SVG also work in relative URLs in Readmes, like PNG does? See #103 (comment) for more info. |
It might be something we'd support in the future. |
I'd love that. Example use: a code coverage tool that directly produces the badge, and simply links to it on the readme. Right now, using |
Update via email:
|
I believe they have fixed this now. @feross can you confirm? |
Yep, confirmed. Feross On Thu, Feb 6, 2014 at 1:58 PM, Thaddee Tyl notifications@git.luolix.topwrote:
|
Looks like GitHub is blocking SVGs again :( See: https://github.com/feross/magnet-uri |
We haven't changed anything in a week or two. Your best bet is to email support@github.com with the output of |
Oh, sorry. Looks like an issue with shields.io. I'll open an issue here. |
I just noticed all the badges on webtorrent returning 404. Emailed github support and got this response:
:( In the meantime I recommend making png the default on img.shields.io to save lots of people from confusion.
The text was updated successfully, but these errors were encountered: