Developing and testing features or extensions for Microsoft Edge
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I'm troubleshooting a layout/rendering issue in Microsoft Edge (Version 130+) and Microsoft Clarity heatmaps for a client's B2B catalog page. When loading The Horeca Store, the dynamic filtering scripts stall on Edge's tracking prevention set to 'Strict', whereas Chrome handles it fine.
Has anyone encountered Edge's Enhanced Security / Tracking Prevention blocking standard JSON-LD or AJAX filters like the ones on this page? Looking for the cleanest header configuration on the server side so Edge users don't get broken filters.
Developing and testing features or extensions for Microsoft Edge
AI answer
No server response header can override Edge Strict Tracking Prevention; keep catalog filtering on a genuinely first-party endpoint, make it work independently of analytics, and use Edge DevTools to identify the exact blocked request before changing CORS or CSP.
Tracking Prevention and Enhanced Security are separate mechanisms:
localStorage, and IndexedDB. Under Strict, analytics and several other tracker categories can have both storage and resource loading blocked. Strict intentionally trades some compatibility for increased privacy.^1^<script type="application/ld+json"> does not perform a request. The relevant failure is more likely the script or endpoint responsible for filtering or injecting that data—not JSON-LD syntax merely being present.There is no documented Edge 130-specific regression in the cited Microsoft material connecting Strict mode, AJAX-generated JSON-LD, and Clarity.
Test in the same Edge profile with Strict still enabled:
Tracking Prevention blocked access to storage for <URL>fetch/XHR requestsEdge documents these Console messages as the way to identify tracking-prevention enforcement; Network then exposes the request and headers behind ordinary network failures.^1^ ^3^
As a diagnostic—not the production fix—disable Tracking Prevention for only this site through the site-information flyout and reload. If the filter immediately works, that confirms a tracking-prevention dependency. Edge also supports adding a trusted site under Settings → Privacy, search, and services → Tracking prevention → Exceptions, but this is an end-user exception and permits all trackers on that site.^4^
For essential catalog behavior:
/api/catalog/filter.async function loadProducts(query) {
const response = await fetch(`/api/catalog/filter?${query}`);
if (!response.ok) throw new Error(`Catalog API: ${response.status}`);
return response.json();
}
loadProducts(new URLSearchParams({ category: "kitchen" }))
.then(renderProducts)
.catch(showFilterError);
// Analytics must remain optional and must not gate renderProducts().
If the API must remain cross-origin, configure CORS for the exact storefront origin. Credentialed requests require client credentials and explicit server permission; a wildcard origin is unsuitable for that case.^5^ The cited page shows ASP.NET Core configuration, but the browser-side CORS requirement applies regardless of the server framework.
CORS or CSP headers can authorize normal browser loading; neither one forces Edge to load a URL that Tracking Prevention has classified and blocked.
Server-render the canonical product JSON-LD in the initial HTML where practical. That is a robustness recommendation so structured data does not depend on filter JavaScript, not evidence that Bing or Edge requires all JSON-LD to be server-rendered.
Clarity is behavioral analytics, so its collection may be unavailable when an analytics resource is blocked. Essential filtering must continue without it.
For a heatmap that is visually stale or unstyled, verify that CSS and fonts are public, permanent, and accessible cross-origin. Clarity caches those assets after first access and does not support resource versioning, so changing content at the same stylesheet URL can leave an older cached version.^6^
If Clarity is serving an old cached stylesheet or font, use the Contact us path on that troubleshooting page and provide:
References