Caching documentation has a side effect with the css

0 Answers 3 Views
General Discussions
Doug
Top achievements
Rank 1
Iron
Iron
Veteran
Doug asked on 04 Nov 2025, 10:33 PM

The documentation at the link below explaining how to prevent the user from having to clear cache when upgrading from one Telerik version to another has an issue with the css priority. My app targets .net 9 but I wasn't able to get the first solution using MapStaticAssets() to work so I implemented the second solution using cache busting. That resolved the caching error but it put the priority of all.css above any css I have in a style element in my component.

In my specific case I have a grid and I want the values in one of the columns to be links but using an anchor element in a grid doesn't underline and turn the content blue so I added css into my style tag in my component:

    .k-grid a {
        color: #0d6efd;
        text-decoration: underline;
    }

That works fine normally, but when I upgraded to the current version of Telerik and had cache issues and followed the cache busting instructions in the link, the content no longer looks like a link. See dev tools screenshots with and without cache busting.

https://www.telerik.com/blazor-ui/documentation/knowledge-base/common-browser-cache-buster

With cache busting it doesn't look like a link because all.css takes priority:

Without cache busting:

Any way to get around this?

No answers yet. Maybe you can help?

Tags
General Discussions
Asked by
Doug
Top achievements
Rank 1
Iron
Iron
Veteran
Share this question
or