starred/radzen-blazor
1
0
Fork 0
mirror of https://github.com/radzenhq/radzen-blazor.git synced 2026-02-04 05:35:44 +00:00
Code Issues 1.3k Packages Projects Releases 22 Wiki Activity

Moving a slider handle to the left/right does not result in the minimum/maximum value #225

New Issue
Closed
opened 2026-01-29 17:33:46 +00:00 by claunia · 3 comments
claunia commented 2026-01-29 17:33:46 +00:00
Owner
Copy Link

Originally created by @PhilippJR on GitHub (Oct 13, 2021).

Describe the bug
When moving a slider handle to the left, it does mostly not stop at the minimum value.
When moving a slider handle to the right, it does mostly not stop at the maximum value.

To Reproduce

  1. Go to slider example page
  2. Move a slider handle to the maximum and see in the log, that it is mostly not 100 but 99 or lower. It is worse when you move the mouse quickly over the right boundary
  3. Observe a similar behavior with the minimum

Expected behavior
Even when moving the mouse quickly far over the boundary the handle value should be the minimum/maximum.

Desktop
OS: Windows 10
Browser: Chrome 94.0.4606.81, Edge 94.0.992.47, Firefox 92.0.1

Originally created by @PhilippJR on GitHub (Oct 13, 2021). **Describe the bug** When moving a slider handle to the left, it does mostly not stop at the minimum value. When moving a slider handle to the right, it does mostly not stop at the maximum value. **To Reproduce** 1. Go to [slider example page](https://blazor.radzen.com/slider) 2. Move a slider handle to the maximum and see in the log, that it is mostly not 100 but 99 or lower. It is worse when you move the mouse quickly over the right boundary 3. Observe a similar behavior with the minimum **Expected behavior** Even when moving the mouse quickly far over the boundary the handle value should be the minimum/maximum. **Desktop** OS: Windows 10 Browser: Chrome 94.0.4606.81, Edge 94.0.992.47, Firefox 92.0.1
claunia commented 2026-01-29 17:33:47 +00:00
Author
Owner
Copy Link

@enchev commented on GitHub (Oct 13, 2021):

image

@enchev commented on GitHub (Oct 13, 2021): ![image](https://user-images.githubusercontent.com/5804953/137128780-8f64694f-18ad-47e4-ae82-e03a0a8820b9.png)
claunia commented 2026-01-29 17:33:47 +00:00
Author
Owner
Copy Link

@enchev commented on GitHub (Oct 13, 2021):

image

@enchev commented on GitHub (Oct 13, 2021): ![image](https://user-images.githubusercontent.com/5804953/137128828-a2a3ee35-104f-42c9-8cbb-1d6c40da2f1e.png)
claunia commented 2026-01-29 17:33:47 +00:00
Author
Owner
Copy Link

@enchev commented on GitHub (Oct 13, 2021):

Ok @akorchev was able to reproduce it and I'm reopening the issue.

@enchev commented on GitHub (Oct 13, 2021): Ok @akorchev was able to reproduce it and I'm reopening the issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#225
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?