Why selecting the current version switches to the home page?

[syeda-git]

Hi,
From the CF216 page, when i select the same CF216 version, the current page stays. This seems to be a good behavior.
https://opensource.hcltechsw.com/digital-experience/CF216/build_sites/practitioner_studio/web_content/

However, if i select an h2 in the same page and then select CF216, the page switches to the home page. Any idea why this is happening?
https://opensource.hcltechsw.com/digital-experience/CF216/build_sites/practitioner_studio/web_content/#hclsoftware-u-learning-materials

Also, why the header title changes from HCL Digital Experience Help Center to Home?

Syed

[kamilkrzyskow]

Hello @syeda-git,
as the version control links do indeed point to the home page of that given version, switching to the homepage is the default behaviour.
Changing to the same page on the different alias is an addition of mkdocs-material:
#4012

mkdocs-material/src/templates/assets/javascripts/integrations/version/index.ts

Lines 93 to 146 in 0559666

	/* Intercept inter-version navigation */
	versions$
	.pipe(
	map(versions => new Map(versions.map(version => [
	`${new URL(`../${version.version}/`, config.base)}`,
	version
	]))),
	switchMap(urls => fromEvent<MouseEvent>(document.body, "click")
	.pipe(
	filter(ev => !ev.metaKey && !ev.ctrlKey),
	withLatestFrom(current$),
	switchMap(([ev, current]) => {
	if (ev.target instanceof Element) {
	const el = ev.target.closest("a")
	if (el && !el.target && urls.has(el.href)) {
	const url = el.href
	// This is a temporary hack to detect if a version inside the
	// version selector or on another part of the site was clicked.
	// If we're inside the version selector, we definitely want to
	// find the same page, as we might have different deployments
	// due to aliases. However, if we're outside the version
	// selector, we must abort here, because we might otherwise
	// interfere with instant navigation. We need to refactor this
	// at some point together with instant navigation.
	//
	// See https://github.com/squidfunk/mkdocs-material/issues/4012
	if (!ev.target.closest(".md-version")) {
	const version = urls.get(url)!
	if (version === current)
	return EMPTY
	}
	ev.preventDefault()
	return of(url)
	}
	}
	return EMPTY
	}),
	switchMap(url => {
	const { version } = urls.get(url)!
	return fetchSitemap(new URL(url))
	.pipe(
	map(sitemap => {
	const location = getLocation()
	const path = location.href.replace(config.base, "")
	return sitemap.includes(path.split("#")[0])
	? new URL(`../${version}/${path}`, config.base)
	: new URL(url)
	})
	)
	})
	)
	)
	)
	.subscribe(url => setLocation(url, true))

This could be a bug with the interception or navigation.instant, so please create an new issue. https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/
However, I see that the linked page uses version 8.5.10 instead of the newest 9.5.2, so please update the version before submitting the issue. I don't remember every issue posted here, so perhaps that was already fixed along the way.

[syeda-git]

@kamilkrzyskow Here's a sample doc built from a recent version of Material for MkDocs. From this page, when you select 2.0 again, it goes to the home page. It doesn't stay on the same page. Is this a bug?
https://syeda-git.github.io/mkdocs-sandbox/2.0/about/

Syed

[syeda-git]

@squidfunk Can you confirm if it is an intended behavior? If yes, is there a way to stop that? If i were to go to the home page, I would click Home.

[squidfunk]

I'm not sure from what I've read. However, as you're on 8.5.10, please first update to the latest version. The problem might have been fixed in the meantime. Updating to the latest version is a prerequisite for a complete and helpful bug report anyway.

[kamilkrzyskow]

@squidfunk The link provided in the recent message: https://syeda-git.github.io/mkdocs-sandbox/2.0/about/ uses version 9.4.8, maybe not the most recent, but according to git blame the file didn't have any relevant changes since then.

The reported issue is being that when a user is on a version branch /2.0/ in the example above, and they click the same version from the toggle it won't "reload the page" keeping the address, but instead loads the home page. So the version navigation isn't intercepted to point to same page of the same version it's only intercepted when selecting another version.

Hence the question.

Can you confirm if it is an intended behavior? If yes, is there a way to stop that? If i were to go to the home page, I would click Home.

[squidfunk]

Please create an issue with a minimal reproduction and exact steps to deploy and we look into it. Doesn't sound intended.

[syeda-git]

@squidfunk #6657