blog output: tag links don't work from pages called with an anchor URL

[aborruso]

Bug description

If I open this URL this URL that contains an anchor

https://quarto.org/docs/blog/posts/2024-07-02-beautiful-tables-in-typst/#cars-heatmap-gt-r

the links of the page tags does not work, the links are not active

Steps to reproduce

• open https://quarto.org/docs/blog/posts/2024-07-02-beautiful-tables-in-typst/#cars-heatmap-gt-r and try to click on a tag

Expected behavior

To have the tag links work

Actual behavior

The tag links not work

Your environment

The env used for quarto website

Quarto check output

The output of quarto website

[mcanouil]

The output of quarto website

That is not the output of quarto check
Could you provide the quarto check output as requested in the template?

The env used for quarto website

That is not your environment.
Please do read properly the issue template.
We expect your environment such as your operating system, etc.

[aborruso]

@mcanouil I reproduced the user experience, it is the blog of the repository of the quarto official website.
For this reason I did not include what was requested in the template.

This is the repo https://github.com/quarto-dev/quarto-web

Should I download the repo locally, render and see if it doesn't work locally by me as well? I don't think so, I think what you see online may be enough.

Thank you always

[mcanouil]

It's not about the reproducible example or not really.
It's really about your environment which is not the one used for Quarto website.
And we have no idea which Quarto and dependencies you are using.

[mcanouil]

It seems you are commenting on a rendered page, but did you reproduce the error? Possibly with a simple example rather that a website/repository as big as Quarto documentation.

FYI, I do reproduce the website issue, including prelease.
https://prerelease.quarto.org/docs/blog/posts/2024-07-02-beautiful-tables-in-typst/#cars-heatmap-gt-r

[aborruso]

Thank you, I close it and open again in the repo of website

[cderv]

This is fine here. Let's not duplicate on the other side.

[cderv]

Problem is in quarto.js. The link processing does not account for anchor part in url

quarto-cli/src/resources/formats/html/quarto.js

Lines 227 to 260 in 962c77e

	async function findAndActivateCategories() {
	const currentPagePath = offsetAbsoluteUrl(window.location.href);
	const response = await fetch(offsetRelativeUrl("listings.json"));
	if (response.status == 200) {
	return response.json().then(function (listingPaths) {
	const listingHrefs = [];
	for (const listingPath of listingPaths) {
	const pathWithoutLeadingSlash = listingPath.listing.substring(1);
	for (const item of listingPath.items) {
	if (
	item === currentPagePath ||
	item === currentPagePath + "index.html"
	) {
	// Resolve this path against the offset to be sure
	// we already are using the correct path to the listing
	// (this adjusts the listing urls to be rooted against
	// whatever root the page is actually running against)
	const relative = offsetRelativeUrl(pathWithoutLeadingSlash);
	const baseUrl = window.location;
	const resolvedPath = new URL(relative, baseUrl);
	listingHrefs.push(resolvedPath.pathname);
	break;
	}
	}
	}
	// Look up the tree for a nearby linting and use that if we find one
	const nearestListing = findNearestParentListing(
	offsetAbsoluteUrl(window.location.pathname),
	listingHrefs
	);
	if (nearestListing) {
	activateCategories(nearestListing);
	} else {

We'll fix this.

[mcanouil]

Thank you, I close it and open again in the repo of website

That's not what I meant. I meant you seem to report an issue on the website that you did not reproduce using a simple reproducible example with Quarto CLI.

[aborruso]

@cderv I also seemed fine here.It was a special case in my opinion, well described, so it didn't make sense to put those two parts of the template. But maybe I'm wrong.

Anyway, thank you very much to you and @mcanouil

[aborruso]

And I'm glad I was helpful. Unfortunately, I don't know how to correct the code

[cderv]

Yes thanks for the report. We'll handle it from here.

It was a special case in my opinion, well described, so it didn't make sense to put those two parts of the template. But maybe I'm wrong.

FWIW I agree with you, it was descriptive enough and reproducible with the website so we can find the issue. This is special case is usually true for JS code part that runs in browser. If is applies on website, then it will most of the time impact our quarto website.

Thank you, this is enough for me to go fix this.