[Blazor] <OverrideHtmlAssetPlaceholders /> Fingerprinting works for scripts but not for stylesheets

[tossnet]

Hello,
I've been working with Blazor WebAssembly Stand Alone and noticed an inconsistency with the OverrideHtmlAssetPlaceholders feature and the #[.{fingerprint}] placeholder system.

✅ For JS Script, it works perfectly as well! The fingerprint is properly generated.

<script src="myscript#[.{fingerprint}].js"></script>

❌However, the same mechanism doesn't work for stylesheets:

<link rel="stylesheet" href="css/app#[.{fingerprint}].css" />

Is there a technical reason why fingerprinting is limited to scripts only? Since the compiler already processes #[.{fingerprint}] placeholders for JS files (both framework and custom ones), wouldn't it make sense for it to also check and process stylesheets in the same way?
Cache-busting is just as important for CSS as it is for JavaScript in production scenarios, and having a consistent approach across all asset types would be very beneficial.
Thank you for your insights!

[hemnaathR]

yeah +1

if renaming the css file is dificult maybe give it a fingerprint option in the query string?
<link rel="stylesheet" href="css/app.css?v=#[.{fingerprint}]" />

[maraf]

I have replied in #64342 (comment) with some technical details. I agree cache-busting is important for all types of files.