Known Firefox Issues

These are the known Firefox issues.

Pages viewed directly from GitHub may not render properly:

This is result of an open Firefox bug carrying over the Content Security Policies (CSP). The restrictive CSP sent by GitHub are applied to the content inserted by the plugin.

Firefox bug tracker bugzilla.mozilla.org#1267027. Last updated 2023-04-07 as at 2023-04-31.

The extension does not automatically view the page (trigger) when navigating to a file:// from a link:

You have to enter the file:// URL directly into the address bar of the browser.

If you do navigate to a file:// URL from a link, click in the address bar and press "Enter" to force the extension to load. Caused by an open Firefox bug to fix this limitation.

Firefox bug tracker bugzilla.mozilla.org#1266960. Last updated 2023-02-22 as at 2023-04-31].

The include:: directive (or any other file:// to file:// request) fails with a CORS or security error:

Firefox isolates every file:// page into its own unique origin, which blocks requests from one file:// document to a sibling file:// resource — for example an include:: target in the same folder or a subfolder. Two separate preferences both need to be relaxed for this to work: privacy.file_unique_origin (origin isolation between file:// pages) and security.fileuri.strict_origin_policy (stricter same-origin enforcement specifically for file:// requests) — disabling only one of the two is not enough.

To work around this:

  1. In a new tab, type or paste about:config in the address bar and press Enter. Accept the risk warning.

  2. In the search box, type or paste privacy.file_unique_origin and pause while the list filters. Double-click the preference to switch it from true (secure) to false (insecure).

  3. Repeat for security.fileuri.strict_origin_policy, also switching it from true to false.

  4. Restart Firefox for the changes to take effect.

    This relaxes origin isolation for all file:// pages, not just this extension.
    This was originally observed with XMLHttpRequest, which the extension and Asciidoctor.js used for all content loading through extension version 3.0. Starting with the 4.0 release, both switch to fetch() instead — confirmed to still be restricted by this same origin isolation, so the workaround above remains necessary.

    See #302.