-
Notifications
You must be signed in to change notification settings - Fork 920
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
Fix icon paths on markdown files #2012
Conversation
Prior to this commit, icons were not properly loading due to path error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your efforts to improve the markdown icons. I'm curious what browser and browser version you are using because, when I look at the markdown in Firefox or Chromium, I see all the icons.
Also, I left some comments on things that were changed beyond simply correcting icon paths.
@finnbear I used Google chrome (113.0.5672.126), safari (16.4) and GitHub Android app (1.113.1). I did not see any icons or illustrations. I can also preview a Markdown file in Visual Studio Code, and icons were not showing. Btw I'm from India, I don't know if that matters! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the PR! Everything looks correct now (simply adding .
before local links).
Interestingly, this makes the icons visible for me in VSCode!
@finnbear after adding the |
Thank you for submitting this pull request! We appreciate you spending the time to work on these changes.
What is the motivation?
Prior to this commit, icons were not properly loading due to path error.
What does this change do?
Changes icon path and comment out not-used icons in markdown files
What is your testing strategy?
It's only a change in icon path in markdown files
Is this related to any issues?
I did not check if there's any issue regarding this!
Have you read the Contributing Guidelines?