Reviews for Markdown Viewer
Markdown Viewer by simov
8 reviews
- Rated 4 out of 5by Paco, 3 years agoDoes what it says on the tin for the most part, doesn't display tables from Reddit correctly though.
- Rated 4 out of 5by MikZ, 3 years agoMy first impression was that it was useless, because it states file:// URLs aren't supported. The docs on GitHub talk mainly about Chrome and the video has no sound, so I didn't find the workaround that somebody else posted in a comment. Here's the fix: https://superuser.com/questions/696361/how-to-get-the-markdown-viewer-addon-of-firefox-to-work-on-linux/1175837#1175837
The fact that this isn't clear in the instructions seems a pretty scathing oversight.
Anyhow, once I added the MIME type, it started working pretty well. - Rated 4 out of 5by 컨트롤D, 3 years agoIt lacked a bit of detail to set the Markdown title to the tab's title when the file was loaded.
- Rated 4 out of 5by Firefox user 16142732, 5 years ago
- Rated 4 out of 5by Firefox user 15492198, 5 years agoIt's an excellant addon,but the support of printing page is poor .the page rendered by this plugin can not be printed completely.
这个扩展很好用,但是对打印的支持不尽如人意。这个插件渲染的页面无法被完整地打印。 - Rated 4 out of 5by Firefox user 13139692, 5 years agoGreat, but Table of Contents sorely needs a dark option.
- Rated 4 out of 5by Max Yudin, 5 years agoThe same problem with the plugin on KDE. In spite of the [MIME solution by Firefox user 15126385](https://addons.mozilla.org/en-US/firefox/addon/markdown-viewer-chrome/reviews/1453572/) works perfectly, I have to refresh the page or change any of settings to see the content instead of blank page.
Plugin v. 3.8
Firefox v. 74.0
P.S. That solution for KDE should have appearance in the Documentation. - Rated 4 out of 5by Firefox user 14300548, 7 years agoGood, but it doesn't correctly interpret code blocks for python
Developer response
posted 7 years agoPrismJS (https://prismjs.com) is responsible for the syntax highlighting, so in case there is a problem with it you have to ask for help there. I can only bump the version in my extension if they have a fix. Other than that fenced code blocks should be used as usual - ```python