61 reviews
  • Add-on works fine on Linux for local .md files using the mime type mod.
    But where do you make the equivalent change for Firefox on OS-X?
  • The markdown viewer is amazing, very neatly done and robust. I even test it on a large .md file with no hiccups.
    my only concern is a recent update recently, where a simple Markdown Viewer is requesting my permission to access personal data of all websites. I'm afraid this is a deal breaker for me. Why would a markup reader want to access my personal info of all my websites?
    I'll gladly update my review and rating once that suspicious permission is tackled.
    thank you
  • I use it to copy the webpage link into LaTeX with the hyperref package. I modify the default markup syntaxis with one appropriate for LaTeX (plus hyperref):

    \href{${page.url}}{${page.title}}
  • Works perfectly on linux after adding mime type.
    Don't forget to click on the toolbar icon to enable markdown rendering for local and web files
    Thanks for the feedback. Good news! With 1.4.0, it's no longer necessary to click the browser icon to request permissions! Yay!
  • Not working. Tried to update mime database but firefox just won't render local and online .md files, even the README.md on github.
  • Exactly as advertised. I open .md or .markdown files in the browser and this "beautifies" them. Many thanks!

    One suggestion I have is to have a "dark mode" that inverts the black on white or to have a "Custom CSS" box in the settings that would allow us to adjust this.

    If this plugin is available on GitHub (haven't checked yet), I might consider making a pull request to implement the feature ^ mentioned above.

    Edit: Fix typo
    Thanks for the feedback! There is a Custom CSS box in settings, and it should do what you want. Try entering " body { background-color: black; color: white } " as the CSS.
  • I cannot make this addon to display a markdown document which is located on my system.
  • Works fine for file opened locally - raw markdown is displayed initially and upon clicking icon it is rendered correctly.
  • If firefox does not correctly assume that your files are UTF-8 encoded, a possible solution (besides using a Byte Order Marker in your file, which is annoying for several reasons) is the following:
    go to about:config and set the intl.charset.fallback.utf8_for_file variable to true. That worked for me.

    This is related to the following bug report:
    https://bugzilla.mozilla.org/show_bug.cgi?id=1071816
    Thank you for the feedback and for this tip! I have added it to the README, and the README is linked from the add-on options page.
  • Note that the author notes that the extension only works "if the content is plain text". That means your browser needs to be rendering the file in a tab already, just without rendering the markdown elements. If it's downloading it instead, the suggestion from 7cac17 below, to add a MIME type for markdown files, worked for me (I'm also on Ubuntu).
  • Markdown that is super effective. Don't know why it is receiving negative reviews.
    Thank you very much for the great review!
  • Does not work at all for me with local markdown files. The effect is that a popup comes up asking what to do with the file, and when selecting "Open in FF" it opens a new tab and brings up the same popup again. Using FF 52.6.0 on RHEL 7.4. I did not try markdown files from a HTTP server.
  • Encoding is not UTF-8
    This is the most common user issue on the project in GitHub. I've now explained in the README file why a BOM is important and supplied workarounds, including setting intl.charset.fallback.utf8_for_file to true, which tells Firefox to assume UTF-8 for local files. You the user have to do this step; the add-on has no way to configure settings. Fortunately, it's really very very easy!
  • Nice add-on, woks fine for me. Maybe just missing the rendering of [TOC] tag.
    Thanks for the great review!
  • For people who found FF keeps asking "what app should be used to open the markdown file", just check the solution (at least for Ubuntu) here: https://github.com/KeithLRobertson/markdown-viewer/issues/2#issuecomment-321940542
  • Utf8 - encoded Chinese documents display messy code, while GB - encoded Chinese documents display normal. Please fix it. Thank you for sharing this practical extension.
    ------------------------
    The problem has been solved. An option to change the default encoding to UTF-8 in about:config: set the value of intl.charset.fallback.utf8_for_file to true. It is perfect now.
  • doesn't work at all
  • didnt work