Prism syntax highlighting is active even when prism_syntax_highlighting is false

[chalin]

Visit the Docsy User Guide section Look and Feel >> Color palette and other styles. This is the first code block of that section, as syntax highlighted by Chroma:

You'll see that only briefly since Prism sweeps over, changing the highlighting to this:

The problem seems to be that MarkMap (#612) is loading prism, as we can see from the Network view:

[chalin]

/cc @nate-double-u @celestehorgan

[chalin]

Actually, if you refresh a few times you might see this syntax highlighting:

This seems to correspond to when there are 404 errors in the console, like these:

GET https://cdn.jsdelivr.net/npm/prismjs@1.23.0/components/prism-mhchem.min.js net::ERR_ABORTED 404

[LisaFC]

Huh, that's very weird (and new - I hadn't updated Docsy-example to the latest Docsy version since last month and it's still using Chroma normally) - I'll look at how the CSS is loading, as as far as I can see I last updated Docsy-example after I merged the Markmap PR.....

[LisaFC]

So it seems to be only happening in the page with the MarkMap diagram in it - if you look at all the other pages, the docs are still using Chroma. Let me see if I can fix it.

[LisaFC]

So I have "fixed" this indirectly by moving the MarkMap diagram to a different page in #750 ...

This does not solve the fact that it seems to be loading the Prism files for some reason (does the code in a MarkMap use Prism by default, I wonder?), which will affect every other code snippet on the page. I'll poke at it some more.

[LisaFC]

AHA. If I take the fenced code block out of our example MarkMap, the other code blocks on the page use Chroma, as specified. I now just need to figure out how to stop it loading Prism (or if it's possible...).

[LisaFC]

Yep, Markmap uses/loads Prism by default - you can switch it off as an option if you're running it from the command line, but we're using an autoloader script that has no parameters. Might file an issue in their repo to see if it's configurable and put a warning/tip in our docs for now - does that make sense?

[chalin]

Good job tracking that down! Sure that makes sense. If that sort of configuration isn't possible, then maybe we can simply document that hardcoded dependency in the user guide.

[chalin]

@LisaFC - any updates?

[LisaFC]

Thanks for the reminder, looks like it should now be possible to disable Prism in the autoloader so I'm going to give it a try...

[LisaFC]

Fixed in #1175