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

Dropdown selects wrong item after update to beta.10 #643

Closed
KonbOgonb opened this issue Jul 22, 2016 · 3 comments
Closed

Dropdown selects wrong item after update to beta.10 #643

KonbOgonb opened this issue Jul 22, 2016 · 3 comments
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@KonbOgonb
Copy link

KonbOgonb commented Jul 22, 2016

Dropdown selects wrong item on bind from model. It selects first one. I have debuged code and seems that the issue is inside domHandler.equals(a,b).
In my case it says that "1" is equal to "2". The type of "value" property of items in options collection is integer. Also this worked fine in previous version (beta 9).

@KonbOgonb KonbOgonb changed the title Dropdown selects wrong item Dropdown selects wrong item after update to beta.10 Jul 22, 2016
@cagataycivici
Copy link
Member

Please provide sample code that replicates it.

@cagataycivici
Copy link
Member

Maybe related to #651 ?

@KonbOgonb
Copy link
Author

KonbOgonb commented Jul 24, 2016

I don't think that it is directly related. To reproduce use [options] collection with numeric value, like
this.cities.push({label:'New York", value:1');
this.cities.push({label:"Rome", value:2);
this.cities.push({label:"London", value:3);
And then let initially selected value be equal to 3 or 2.
You are using domHandler to comare values, and look what it says when we are comparing two different numbers, like 1 and 5. http://bit.ly/2ai6y9n

@cagataycivici cagataycivici added the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Jul 25, 2016
@cagataycivici cagataycivici added this to the 1.0.0-beta.11 milestone Jul 25, 2016
@cagataycivici cagataycivici self-assigned this Jul 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

2 participants