[dev-v5][ValidationMessage] Fix displaying multiple messages on top of each other#5016
Merged
Merged
Conversation
|
✅ All tests passed successfully Details on your Workflow / Core Tests page. |
Summary - Unit Tests Code CoverageSummary
CoverageMicrosoft.FluentUI.AspNetCore.Components - 98.9%
Microsoft.FluentUI.AspNetCore.Components.Charts - 100%
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses issue #5008 by changing how FluentValidationMessage renders multiple validation messages so they no longer overlap in the FieldMessage slot, and it updates the Forms documentation to match the current configuration API.
Changes:
- Render all field validation messages inside a single
FluentTextinstance instead of emitting multiple slotted elements. - Add styling adjustments on
FluentValidationMessage(noting potential interaction with existing CSS isolation). - Fix the documented configuration property name (
UseNativeConstraintValidationUI).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| src/Core/Components/Forms/FluentValidationMessage.razor.cs | Adds inline style to the component’s style builder (needs to be reconciled with existing CSS isolation). |
| src/Core/Components/Forms/FluentValidationMessage.razor | Consolidates message rendering into one FluentText and inserts separators between messages. |
| examples/Demo/FluentUI.Demo.Client/Documentation/Components/Forms/Forms.md | Updates documentation to use the correct configuration property casing (...UI). |
dvoituron
requested changes
Jul 14, 2026
- style through isolated css
dvoituron
requested changes
Jul 14, 2026
….com/microsoft/fluentui-blazor into users/vnbaaij/dev-v5/fix-issue-#5008
dvoituron
approved these changes
Jul 15, 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
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.
Fix #5008 by rendering the messages in a loop within a
fluent-textinstead of rendering afluent-textper message in a loopBefore
After