Skip to content
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

RangeSelector sets RangeStart property to value of Minimum property #4988

Open
14 tasks
p0lny opened this issue May 16, 2024 · 0 comments
Open
14 tasks

RangeSelector sets RangeStart property to value of Minimum property #4988

p0lny opened this issue May 16, 2024 · 0 comments
Labels
bug 🐛 An unexpected issue that highlights incorrect behavior

Comments

@p0lny
Copy link

p0lny commented May 16, 2024

Describe the bug

When the RangeSelector range is set for example to [-100; 100], and the bound lower property is set to 0, the value is overwritten to Minimum value of RangeSelector.

Regression

No response

Reproducible in sample app?

  • This bug can be reproduced in the sample app.

Steps to reproduce

1. Add RangeSelector to your page.
2. Set Minimum and Maximum properties to -100 and 100.
3. Prepare bindable properties for RangeStart and RangeEnd properties
4. Set value of bindable property for RangeStart to 0
5. The value will be overwritten to RangeSelector Minimum property value (-100)

Expected behavior

The value is not beeing overwriten - should stay 0.

Screenshots

No response

Windows Build Number

  • Windows 10 1809 (Build 17763)
  • Windows 10 1903 (Build 18362)
  • Windows 10 1909 (Build 18363)
  • Windows 10 2004 (Build 19041)
  • Windows 10 20H2 (Build 19042)
  • Windows 10 21H1 (Build 19043)
  • Windows 11 21H2 (Build 22000)
  • Other (specify)

Other Windows Build number

No response

App minimum and target SDK version

  • Windows 10, version 1809 (Build 17763)
  • Windows 10, version 1903 (Build 18362)
  • Windows 10, version 1909 (Build 18363)
  • Windows 10, version 2004 (Build 19041)
  • Other (specify)

Other SDK version

No response

Visual Studio Version

No response

Visual Studio Build Number

No response

Device form factor

No response

Nuget packages

No response

Additional context

No response

Help us help you

No.

@p0lny p0lny added the bug 🐛 An unexpected issue that highlights incorrect behavior label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 An unexpected issue that highlights incorrect behavior
Projects
None yet
Development

No branches or pull requests

1 participant