Doesn't work with FF 34.0.5

[davidegiannella]

After the update to FF 34.0.5 whenever I try to open a local .md file, it prompts me with what I want to open it (let's say emacs) rather than viewing it in the browser itself.

[cmtonkinson]

Or 36.0.4

[klonos]

Just for the record, it works for me in fx 39.0a1 x64 latest builds. I guess you guys will have to wait until that version is released as stable 😄

[Thiht]

With the version 36 aurora, I had this problem with the built-in pdf.js (it prompted to download the pdf instead of reading it). Can you try to completely reinstall Firefox, including config files, preferences, etc. ? It worked for me with pdf.js

[fpirsch]

Everything fine here with FF36 Ubuntu and Windows.

[MaerF0x0]

No worky for 37.0.1 on OS X

[davidegiannella]

Tried to start firefox, 37.0.1 this time, with a new profile having only MD viewer installed but still it doesn't work. Seems we'll have to wait for FF 39.

[hahcho]

The same with firefox 38.0-1 on Arch.

[dizzib]

Same problem after upgrade FF from 38.0 (where it was working nicely) to 38.0.5 as part of a full system upgrade in Arch Linux. Problem even persists after downgrade back to 38.0.

[klonos]

Still works fine in 41 nightly builds. Must be some kind of regression in 38.

[fpirsch]

This is NOT related to FF 38. It works fine here with 38 and 38.0.5 on both Ubuntu and Windows, I'm using it every day.
This problem must be somewhere else, e.g. in the OS config.

[RGBD]

Do not work with local files.
Firefox 39.0
Both Fedora 22 and Arch Linux.

[davidegiannella]

what details can I provide for better investigate and reproduce this issue? FF 39.0 and still not working.

I played around though so maybe can be something else now.

[wangjiezhe]

It doesn't work for me on firefox 39.0-1 on arch.

[Thiht]

Progress report: I was able to reproduce the "not working" bug on Fedora with FF39, so I guess there was a change in FF's API or something. I tried several minor modifications on my side but weren't able to make it work yet... So some investigations will be needed on what could be broken. As far as I can tell, it may require checking on FF's source code since the doc on streamconverters is kinda sketchy. It could take a while before it works again.

Could some of you (with the bug) try these two add-ons and tell here if they work, so I can compare what differs with markdown viewer ?

• https://addons.mozilla.org/fr/firefox/addon/jsonview/
• https://addons.mozilla.org/fr/firefox/addon/open-in-browser/

[wangjiezhe]

The first one work fine for me,

but the second doesn't with local files.

[raphael0202]

It also doesn't work for me, I get a prompt asking where to save the file. On Fedora 22, Firefox 40.0.3

[RGBD]

Not working. Firefox 41.0.1 x86_64 Arch Linux

[WnP]

@Thiht both jsonview and open-in-browser works as expected here on firefox 40.0.3, but markdown-viewer doesn't render mardown at all

[WnP]

setting:

<RDF:Description RDF:about="urn:mimetype:text/plain"
        NC:value="text/plain"
        NC:fileExtensions="md"
        NC:description="Text Document">
    <NC:handlerProp RDF:resource="urn:mimetype:handler:text/plain"/>
</RDF:Description>

in ~/.mozilla/firefox/*default/mimeTypes.rdf fix this issue for me

all credits are for Ryan Chapin, original article: source

[Thiht]

I think I finally found the fix, now working on my Fedora 22/Firefox 42.0. :)

Can I have some feedback before I push the changes to addons.mozilla?

[Thiht]

If you want to try the fix I published a pre-release here: https://github.com/Thiht/markdown-viewer/releases/tag/v1.9-pre
Note it won't work if electrolysis is enabled (Firefox 43+ I think), see #46.

[wangjiezhe]

It now works fine for me on firefox 42.0 on Arch

[Thiht]

Cool, I'll update the AMO version later today :)

[Thiht]

I just updated the new version to AMO, it should be updated in a few days if nothing goes wrong. I suggest you switch back to the signed version when it's updated to obtain possible future updates.

[davidegiannella]

Sorry for very late reply. I can confirm that the 1.9 version fix the issue. Thanks @Thiht