fix(#799): flips min and max labels to match the selected value#804
Merged
Conversation
🦋 Changeset detectedLatest commit: a4d1016 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
garethbowen
commented
May 6, 2026
| /> | ||
| <div class="range-bound range-min"> | ||
| {{ start }} | ||
| </div> |
Collaborator
Author
There was a problem hiding this comment.
This move wasn't strictly necessary but it feels more logical for both vertical and horizontal to have the min and max labels beside each other.
latin-panda
approved these changes
May 7, 2026
Collaborator
latin-panda
left a comment
latin-panda
left a comment
There was a problem hiding this comment.
You've killed so many fleas in this feature 😅
Collaborator
Author
I got sick of being bitten! 🤕 |
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.
Closes #799
I have verified this PR works in these browsers (latest versions):
What else has been done to verify that this works as intended?
Why is this the best possible solution? Were any other approaches considered?
The other option would be to keep the labels where they were and invert the value out of the primevue widget. However I think the min should be at the bottom, and this is consistent with other implementations, so should be more intuitive.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Do we need any specific form for testing your changes? If so, please attach one.
What's changed
I put the min label at the bottom of the slider, and the max label at the top.