-
Notifications
You must be signed in to change notification settings - Fork 1.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
Most image links are broken when viewing an app #1989
Comments
Looking at the source code, it seems the problem is that each relative images found in readme are modified here: Lines 108 to 111 in 434b074
Problem is that GitHub now uses CORS to prevent resources from being loaded from another domain, so links like this will be broken. |
Actually that's weird: links like this one generated by the I tried to create a simple html file that embbeds the same img file in a personal web server and it works: https://warpdesign.fr/tests/gh/ Not sure why it doesn't work as expected on |
I believe it is because of the headers:
|
I'm seeing the same thing for all images in Edge. |
YouTube embeds are also broken, seemingly also due to CORS. |
I've got a solution for the image URL's that doesn't involve changing server configuration: Loop through image elements in the README, Edit: this must be done by those who maintain electronjs.org |
I think I found a way to fix CORS errors without touching the server: #2000 |
@warpdesign Cool! Do you know if the YouTube embeds can also be fixed in a similar way? |
I'm not sure. Could you give me a link to an app with such an embed in its description? |
@warpdesign Here's one: https://www.electronjs.org/apps/wayward The embedded URL is https://www.youtube.com/embed/kc69XEXiPzE, a perfectly functional embed URL... but cross-origin headers block it. |
@yikuansun I'm afraid there is nothing that can be done for YouTube embeds: the server's CORS rules are too strict and the |
See https://www.electronjs.org/apps/react-explorer
These images come from the README.md of the repository.
The text was updated successfully, but these errors were encountered: