fix(VProgressLinear): guard opacity against undefined props to prevent NaN in SSR#22880
Merged
J-Sek merged 1 commit intoMay 31, 2026
Merged
Conversation
J-Sek
approved these changes
May 31, 2026
J-Sek
added
T: bug
J-Sek
pushed a commit
that referenced
this pull request
May 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 #22876
When
bgOpacityorbufferOpacityprops are unset,parseFloat(undefined)evaluates toNaN. In CSR the DOM silently rejects it, but in SSR Vue serializesNaN(which hastypeof === "number") asopacity:NaN;in the HTML — invalid CSS that fails W3C validation.Added null checks so the inline opacity is only set when the prop is explicitly provided. When unset, the CSS variable fallback (
opacity: var(--v-border-opacity)) applies as intended.