New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(number-field): update button label to use number-field-labels as part of the text #3474
Conversation
Tachometer resultsChromenumber-field permalink
search permalink
slider permalink
textfield permalink
Firefoxnumber-field permalink
search permalink
slider permalink
textfield permalink
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Please review the failing tests in this branch. |
@Westbrook Here's some explanation for these changes... I'd love to get your opinion on this. |
updated the logic such that textField takes care of setting up the labels on the input properly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is looking good, just some small clean up remains.
Together with that, please take a look at this test and include a similar one here to support preventing regressions in this area going forward.
updated the code to add a test and fixed the code styling issues @Westbrook |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great. Thanks for adding the test.
9c139a9
to
118da9c
Compare
Updated the Number field increase/decrease buttons to use the number fields label as part of their label text
Description
Previously the number field increase/decrease buttons were using hardcoded labels as Increment/Decrement but now with this update buttons label text would use the number-field-label text as a part of it to give more context and clarity.
So for
The buttons would have their labels as "Increase Package width" and "Decrease Package Width".
Related issue(s)
Motivation and context
How has this been tested?
Screenshots (if appropriate)
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main
.