Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Regression: cannot select the last option in <select> with ng-options #10161

Closed

Description

@BenoitBorlee

I have a select directive with ng-options on a simple array of strings :

<select ng-model="formData.mySelect" ng-options="o for o in ['A','B','C']"></select>

With angularjs 1.2.27, I cannot select the last option ('C') the first time. I can only select other entries.

Reproduced here :
http://jsbin.com/pahujutico/1/watch?html,js,output
Steps :

  • Select the 'C' option of the selection box at first.
  • Please note that 'C' is NOT displayed.
  • Select the 'A' option of the selection box.
  • Please note that 'A' is displayed.

It works well with angularjs 1.2.25.

Activity

  1. lgalfaso commented on Nov 21, 2014

    @lgalfaso
    Contributor

    it looks like a real bug, let me see if it is possible to fix this quickly

  2. self-assigned this
    on Nov 21, 2014
  3. added this to the 1.3.5 milestone on Nov 22, 2014
  4. lgalfaso commented on Nov 22, 2014

    @lgalfaso
    Contributor

    it looks like this is an actual issue even on 1.3. #10166 is tracking the fix for 1.3, once this landed I will back port the fix to 1.2

  5. pkozlowski-opensource commented on Nov 29, 2014

    @pkozlowski-opensource
    Member

    @lgalfaso looks like #10166 landed already. Do you need a hand with back-porting it to 1.2.x?

  6. modified the milestones: Ice Box, 1.3.6 on Dec 1, 2014
  7. Narretz commented on Dec 1, 2014

    @Narretz
    Contributor

    Is it sensible to track the backport to 1.2 under the 1.3.x milestones? Should we have another milestone that tracks 1.2.x issues?

  8. pkozlowski-opensource commented on Dec 1, 2014

    @pkozlowski-opensource
    Member

    @Narretz if this is cherry-pickable to 1.2.x than we should do it IMO

  9. guilbep commented on Dec 12, 2014

    @guilbep
    Contributor

    Seems like the same as #10213

  10. removed their assignment
    on Dec 14, 2014
  11. petebacondarwin commented on Jan 11, 2015

    @petebacondarwin
    Contributor
  12. petebacondarwin commented on Jan 25, 2015

    @petebacondarwin
    Contributor

    We are not going to backport this to 1.2.x since that branch is only receiving security fixes now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions