What you can do is have a companion app to read the local files (will require user's permission) and communicate with the extension via native messaging. Thanks for your reply! Not sure how it's gonna work as I want to read the "current" file and periodically read the content again (to watch changes). For instance, the user will type file:///path/to/README.txt (written using AsciiDoc lightweight markup) and the extension will convert the AsciiDoc document to HTML 5 and display the result. If the user edit the file /path/to/README.txt, then the extension will display the updated version. File URLs are not supported currently. If this is something you would like to see, please send us feedback via Feedback Assistant with your use cases for wanting local file access. Thanks! Ok I will do, thanks Timothy. In my opinion, file:// URLs are particularly useful to render local files written using lightweight markup (Markdown, AsciiDoc...).

This is not working. I have Safari 14 installed on Catalina end even set it as default browser. Still getting: Same here. I'm running: $ xcrun safari-web-extension-converter /path/to/extension-dir safari-web-extension-converter requires at least Safari 14.0 to run. Unable to parse manifest.json at file:///path/to/extension-dir The manifest.json can be seen at: https://github.com/asciidoctor/asciidoctor-browser-extension/blob/master/app/manifest.json Anyone has a solution or a way to troubleshoot this issue?