Reviews for Markdown Viewer Webext
Markdown Viewer Webext by Kulero, Cimbali
12 reviews
- by James Cherry, 4 months agoRated 1 out of 5This 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.
Developer response
posted 4 months agoI’m sorry to hear about your experience. Local files are tough to handle between the mime types, operating systems, Firefox… Hopefully the support will improve with future Firefox versions, but I’m afraid there’s nothing more the add-on could be doing. - by Firefox user 15235351, 2 years agoRated 1 out of 5Considered 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. - by Roselove, 2 years agoRated 1 out of 5Doesn't work. There's no button, and opening a local file on Linux still tries to download it.
- by NatoBoram, 2 years agoRated 1 out of 5Doesn't work. There's no button, and opening a local file on Linux still tries to download it.
- by Firefox user 13434693, 3 years agoRated 1 out of 5Not working. Tried to update mime database but firefox just won't render local and online .md files, even the README.md on github.
- by Firefox user 13809707, 3 years agoRated 1 out of 5Does 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.
- by Firefox user 10391247, 4 years agoRated 1 out of 5Just remplaced Markdown Viewer on firefox 55.0.3 , OSX.
Does not recognize .md local files. Got FF asking what to do with the file.Developer response
posted 4 years agoI'm sorry you are unable to use the addon as needed. But I believe the problem is that FF never hands over control of the document to the addon. Check Issue #2 on the github page where there are (links to) configuration steps which have worked on Linux. Perhaps they will work on OSX. Please try them and comment on the issue what steps you took and what happened. Thanks.