-
Notifications
You must be signed in to change notification settings - Fork 380
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
[FluentSlider] [FluentNumberField] Fix #2948 #3077
Conversation
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.
Will test this soop
I've fixed the unit test by easing the BUnit JSInterop mode. I'm not sure if that breaks any testing conventions. Should this be split into two PRs? One for |
Found another issue with my fix for When typing directly into the control, it would flicker and lose the change. |
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.
Next time, please create one PR to fix one problem. This makes it easier to maintain the code.
Thank you :-)
Pull Request
📖 Description
Fixes issues reported in #2948. Two issue reported both related to changing the value of the control programatically.
🎫 Issues
The underlying issue is that the web components being wrapped were designed to have there states only changed interactively.
bind-value
does not behave as expected. Inward binding works only on for initialization. Outward binding works as expected.This gives the appearance of a sync issue.
👩💻 Reviewer Notes
FluentSlider
- #2665 did not fully fix #2609. The original fix was to prevent the flickering when the slider was moved rapidly originally reported. I was not able to reproduce this problem with the current implementation ofFluentDataGrid
. I did end up adding debouncing with theDebounceAction
. I believe I did this correctly.FluentNumberField
- The fix was to ensure the underlying web component reflected the correct value. I could not find a way of distinguishing if the value was changed by manipulating the control or if it was changed programatically. I opted to use some javascript to force the value in the web component. I also added aDisposeAsync
. It was missing.I've also included an
issue-tester
page as part of this draft📑 Test Plan
✅ Checklist
General
Component-specific