fix: resolve font loading issue with experimental.inlineCss enabled #83707
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes: #83674
What?
Fixed font loading issue when
experimental.inlineCss
is enabled. Fonts were not loading properly in production builds because font CSS files containing@font-face
declarations were not being included in the CSS inlining process.Why?
When
experimental.inlineCss
is enabled, CSS files are inlined as<style>
tags instead of being loaded as separate files. However, the CSS filtering logic inClientReferenceManifestPlugin
was not properly including font CSS files, causing fonts to fail to load in production builds.How?
ClientReferenceManifestPlugin
to:@font-face
declarations are preserved when CSS is inlined