Javascript clashing with quarto-nav.js

[baptiste]

I'm trying to use the lightgalleryjs library to display collections of photos on my quarto website. Unfortunately, there's a glitch, and after some trial and error I've narrowed it down to a clash with quarto-nav.js. If I comment it out manually in the html, the gallery behaves as expected; if I uncomment it, the lightbox view fails to load the second image (spinning wheel). My test webpage is here:

https://baptiste.github.io/quarto-gallery/

with the manually edited html

and here's a screenshot of the bug when quarto-nav is present

I'm not exactly sure of what quarto-nav does, or how/if I can selectively tell quarto not to include it. Alternatively, I'd like to find a way to make the two js scripts coexist peacefully, but I don't know how to isolate the problem (let alone fix it); the web console didn't return an obvious error I could understand.

[dragonstyle]

Sorry you've run into this. When I visit the gallery (very nice layout BTW!), I am able to use the gallery feature without any errors or issues. I'm not sure whether you've fixed the issue or something else change or if perhaps the issue is local to your machine (e.g. perhaps a cached version of something)? Anyhow if you are able to still reproduce this I would love to track it down and fix it!

[baptiste]

@dragonstyle should I open an issue?

[dragonstyle]

This should be fixed in the next update of Quarto 1.3 (I just started a build with the fix). We were always adding an href attribute to document links, which appeared to be confusing lightGallery.

1bc73c7

[baptiste]

Nice! Thanks a lot, that did fix it.

[baptiste]

The href="" seems to be back? I'm only getting back to this photo gallery idea now, and looking at the HTML produced by Quarto (1.4.322) shows this href="" being introduced (hard-coded).

[dragonstyle]

Can you let me know where you're seeing this? We didn't change the fixed behavior, but it is possible that it leaked in somewhere else...