Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

Slider overwrites value when attributes in wrong order #3521

Open
basdecort opened this issue Aug 9, 2018 · 2 comments
Open

Slider overwrites value when attributes in wrong order #3521

basdecort opened this issue Aug 9, 2018 · 2 comments
Labels
e/7 🕖 7 help wanted We welcome community contributions to any issue, but these might be a good place to start! inactive Issue is older than 6 months and needs to be retested t/bug 🐛 up-for-grabs We welcome community contributions to any issue, but these might be a good place to start!

Comments

@basdecort
Copy link

Description

Slider overwrites the provided value when Xaml attributes in wrong order.

Steps to Reproduce

  1. Add a Slider to your Xaml with Value attribute followed by Maximum and/or Minimum attribute.
  2. Provided value will be ignored, 1 will be used as default value.

Expected Behavior

Provided value is used, regardless of order of attributes.

Actual Behavior

Provided value is overwritten with 1.

Basic Information

  • Version with issue: 3.1.0.697729
  • Last known good version: -
  • IDE: Visual Studio for Mac
  • Platform Target Frameworks:
    • iOS: 11.4
    • Android: 8.1
    • UWP: -
  • Android Support Library Version: 27.0.2.1
  • Nuget Packages: Xamarin.Forms 3.1.0.697729
  • Affected Devices: reproduced on iPhone X and Samsung Galaxy S6

Reproduction Link

SliderIssue.zip

@samhouts
Copy link
Member

Part of #1943

@samhouts samhouts moved this from New to Ready For Work in Triage Aug 10, 2018
@samhouts samhouts added this to To do in Other Ready For Work Oct 15, 2018
@samhouts samhouts removed this from Ready For Work in Triage Oct 15, 2018
@samhouts samhouts added the inactive Issue is older than 6 months and needs to be retested label Feb 6, 2019
@samhouts samhouts added help-wanted up-for-grabs We welcome community contributions to any issue, but these might be a good place to start! help wanted We welcome community contributions to any issue, but these might be a good place to start! and removed help-wanted labels Jun 28, 2019
@charlesroddie
Copy link

Solution here: #1943 (comment)

@samhouts samhouts removed the inactive Issue is older than 6 months and needs to be retested label Feb 6, 2020
@samhouts samhouts added the inactive Issue is older than 6 months and needs to be retested label Jul 17, 2020
@samhouts samhouts added this to the 5.0.0 milestone Aug 13, 2020
@samhouts samhouts added this to To do in vNext+1 (5.0.0) Aug 14, 2020
@samhouts samhouts removed this from the 5.0.0 milestone Nov 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
e/7 🕖 7 help wanted We welcome community contributions to any issue, but these might be a good place to start! inactive Issue is older than 6 months and needs to be retested t/bug 🐛 up-for-grabs We welcome community contributions to any issue, but these might be a good place to start!
Projects
Development

No branches or pull requests

3 participants