This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Bug with select binding to an array of integers #9700
Description
I am trying to bind an array of integers to a select using 1.3.0. There is a difference if the array is populated when the controller is initialized versus after an event occurs. If it's populated after an event, the wrong item is selected.
http://jsfiddle.net/fwanicka/n0sbeuab/ (array populated when controller initialized)
http://jsfiddle.net/fwanicka/6sx152dm/ (array populated after a timeout/event)
The second fiddle works in 1.2.23, so this is a breaking change from that version, which we just upgraded from:
http://jsfiddle.net/fwanicka/6s5rzz9j/ (array populated after a timeout/event using 1.2.23)
Activity
kentcdodds commentedon Apr 28, 2015
This issue is still broken in 1.3.15 but it is fixed in 1.4.0-rc.0 http://jsfiddle.net/8xc9pctd/2/
Narretz commentedon Apr 28, 2015
It's unlikely that this is going to be fixed in 1.3.x, because ngOptions was pretty heavily refactored.
----- Ursprüngliche Nachricht -----
Von: "Kent C. Dodds" notifications@github.com
Gesendet: 28.04.2015 15:36
An: "angular/angular.js" angular.js@noreply.github.com
Cc: "Martin Staffa" mjstaffa@googlemail.com
Betreff: Re: [angular.js] Bug with select binding to an array of integers(#9700)
This issue is still broken in 1.3.15 but it is fixed in 1.4.0-rc.0 http://jsfiddle.net/8xc9pctd/2/
—
Reply to this email directly or view it on GitHub.
petebacondarwin commentedon Sep 13, 2015
This will not be fixed in 1.3