Tom Rumpf

# Workaround You can fix this by overwriting `onPointerDown` to `{(e) => e.preventDefault()}` on the `` & adding an `onClick` event & `onOpenChange`. Before: ```typescript return ( {/* trigger content...

@huozhi this might be of interest to you, since you were working on https://github.com/vercel/next.js/pull/61088

This even happens in this minimal minimal example: ```typescript import { MetadataRoute } from "next"; export async function generateSitemaps() { return [ { id: 1 }, { id: 2 },...

@meh7an if you are looking for a solution in the meantime (not statically generated). You can create an `/app/sitemaps/products/[id]/route.ts` (for example) endpoint and create your sitemaps there. Here's an example:...

Yep, also using this for the index like `/app/sitemaps/index.xml/route.ts`, which then ends up looking like: ```typescript import { URLS } from '../../../common/configs/urls'; import { fetchProducts } from '../utils/fetchProducts'; import {...

Can confirm this issue is fixed in `Next.js 14.1.1-canary.82` when I just tried it with my reproduction. Thank you @huozhi & @abhinaypandey02 ❤️

This sounds like something's up with your code. Are you maybe redirecting to `/contact/` -> `/contact`? The TopLoader only shows if the new url is not the same.

same happening here 👋 I think this is an issue because of Mac, and it using `event.metaKey` not ctrlKey? Since this is taking a long while to fix and PRs...

You can do this in [Holy Loader ↗](https://github.com/tomcru/holy-loader) ```typescript 'use client'; import { startHolyLoader } from 'holy-loader'; startHolyLoader(); router.push('/your-page') ```

That's a good catch and it makes sense that it shouldn't trigger on URL states like these. I have some ideas in mind I'll try out! ✌️