-
Notifications
You must be signed in to change notification settings - Fork 459
Revert "[FluentSlider] Use current-value instead of value attribute in web component" #2591
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
Conversation
…n web co…" This reverts commit 0f6d06a.
|
✅ All tests passed successfully Details on your Workflow / Core Tests page. |
Summary - Unit Tests Code CoverageSummary
CoverageMicrosoft.FluentUI.AspNetCore.Components - 61%
|
|
So, how can I change the value of the FluentSlider externally, rather than just setting its initial value? Let me give an example: I want to change the value of the FluentSilder using the mouse wheel, and also be able to set the value by dragging the FluentSlider. Currently, after dragging it once, the |
|
The slider was/is not intended to work in conjunction with the mouse wheel. You can change the value by clicking/dragging or by keyboard left/right arrows. |
…n web component" (microsoft#2591) * Revert "[FluentSlider] Use current-value instead of value attribute in web co…" This reverts commit 0f6d06a. * Re-add binding test
Reverts #2438
When using
current-valueinstead ofvalue, on Blazor Server the Slider will get stuck in an update loop when moving the tick around quickly. I've tested which other effects there could be with usingvalueand haven't found any.