Extremely useful extension for viewing local .md files as HTML! And the Table of Contents feature is indispensable!! Thank you!

I had a Markdown file (*.md) on disk I needed to render and print. It took about 30 seconds to install this extension, drag-and-drop the file onto a Firefox window, and boom, there's the rendered version of the file displayed as intended. I'm using Firefox 84.0.1 on Windows 10. Thank you!

great extension!

This used to work really well. With firefox 83.0 on OSX 14.1 it cannot render a local file. I wasted way too many hours trying all the work-arounds described in the github page and on superuser. None of them worked.

The syntax highlighting options are nice, but if you have an URL in a code block, the double-slash is interpreted as a JS comment.

Excellent

this add on works perfectly in firefox v64
And i love the size of this add on
Thanks a lot Mr. Keith L Robertson

I had to follow the instructions on the home page to set up the markdown mime type on linux, and with that it works marvelously.

Does not work if the .md extension is in upper case.

Considered installing but the excessive permission requirements put me off.
Please be clear WHY the extension needs 'Access your data for all websites' as a permission requirement if it will be accessing only local data.

Not working!

It took me a while to even get it to do anything. I would appreciate proper instructions on how to use the extension.

This is not a problem with this extension, rather with Firefox. Whenever I open markdown files in firefox, it just wants to download them. I ended up having to change the mimetype text/plain to also include the extensions .md and .markdown. See here: https://superuser.com/questions/696361/how-to-get-the-markdown-viewer-addon-of-firefox-to-work-on-linux/1175837#1175837

The way the superuser article fixes the problem involves making all markdown files part of the text/plain mimetype but other apps on KDE (and possibly other 'DEs) use the text/markdown mimetype differently than text/plain. So I went into about:config and changed helpers.private_mime_types_file to a custom file (e.g. ~/.firefox-mime.types) to separate firefox's mimetypes from my system. I then added "text/plain md markdown" in that file. The problem is due to the way firefox handles files and mimetypes.

I am unable to change the code style in the markdown-viewer menu which is very frustrating, the markdown style does work.

It works. For those like me using Linux, you should read the README in https://github.com/KeithLRobertson/markdown-viewer/blob/master/README.md#installing-on-linux At first it seemed like it was a no go but after reading the docs and following the procedure, the extension works just fine.

Doesn't work. There's no button, and opening a local file on Linux still tries to download it.

This is pretty good and does what I want. You can open a a markdown (.md) file on your machine in Firefox. There are multiple ways to style the page.

By default a small enlargable box is top left and you can click on this to get 3 options.

The first allows you to switch between the default and GitHub markdown style. (no utf-8 on one?).

The second has a decent list of styles that would be good but this didn't work for me.

The final option is a button to download the file as HTML. This works though the HTML is rather messy as it has all the code and styling for the dropdown box. You can remove the dropdown box though in the app’s settings though then of course you can’t click it to save as HTML. However you can delete the excess code from the file if you want to, though it's an extra step.

At least three other ways exist to to style pages. One is to write custom styles in the text box on the apps settings page. This is good for default styles.

Another way is to link to an external CSS file (put the link at the bottom of the page otherwise it won't work properly). You can also use an embedded stylesheet anywhere on the page (between two style tags).

All in all this is a great little add-on. Loses a mark from me because the dropdown styles didn't work for some reason and the generated HTML was messy.