Update Blazor components with appearance-readonly and full-bleed #2619
Conversation
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
…r-field, and nimble-text-field to support appearance-readonly and full-bleed
mollykreis
requested review from
rajsite,
atmgrifter00 and
msmithNI
as code owners
rajsite
approved these changes
May 28, 2025
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.
Pull Request
🤨 Rationale
We've recently added
appearance-readonlyandfull-bleedto some components in nimble. These attributes need to be exposed in the Blazor components.👩💻 Implementation
appearance-readonlyto the combobox, select, text field, number field, and text area Balzor componentsfull-bleedto the combobox, select, and number field Balzor componentsframelessappearance to the number field appearance modes and the drop-down appearance modes🧪 Testing
New unit tests
✅ Checklist