Typeahead broken in angular 1.3.0-rc.1 (even worse, than since beta.11)

[EvAlex]

Example (docs-based): http://plnkr.co/edit/jQSozNWRAbRtrGuOGxb4

Typeahead for states with flags has following bugs (some of them duplicate those reported in other issues, but the last one is new I guess):

• Selecting with mouse doesn't work (this appeared in beta.11 and is already reported in other issues)
• Selecting with arrow keys doesn't work too
• Flags icons not appearing
• Selected object is rendered as '[object Object]'

Just change angular version to 1.3.0-beta.9 and everything gets fine.

[Siyfion]

Agreed, it is very broken. To see this when Angular 1.3.0 is now at release candidate stage is slightly worrying, I hope it gets fixed soon. 😟

[andreychev]

Agreed. More info: angular/angular.js@1eda183

[antoinepairet]

#2602 solved all issues using angular up to 1.3.0-beta.19. It will be part of 0.12
However, with 1.3.0-rc.0 and 1.3.0-rc.1, the Selected object is rendered as '[object Object]'

@pkozlowski-opensource, what is your opinion regarding 1.3.0-rc.x ?

You can have a look at these plunkr:
http://plnkr.co/edit/N7MBdrDF8SAZ8Yo8DVS6?p=preview
http://plnkr.co/edit/gmOcZlb1KOtQm7D34PZZ?p=preview

[chrisirhc]

Interesting find. It looks like in order to support selecting objects you would need to replace that formatter added by the input type using your own directive.

I suggest that we add a directive that does that (replace the default formatter) and add a note for users to add that directive if they need to select objects, when upgrading to AngularJS 1.3.

Replacing the formatter makes assumptions that there are no other formatters added by the user. As such, it's not safe to do this by default for all users. Some users might actually want the coercion to string since it's AngularJS's new default behavior for text inputs.

[SonicGD]

Any news on this issue? We want migrate to 1.3, but this is stopper for us.

For us too.

[ribizli]

Regarding problem with $formatters ([object Object]): setting directive priority to 1 lets Typeahead's formatter run first (with the 'not toString()'d version).

[mpaulucci]

+1 for this issue

[chrisirhc]

Waiting on 1.3 to stabilize a bit more before working on this. angular/angular.js@1064443 , part of 1.3.0-rc.4 has already changed some of the behavior in the original issue (objects no longer renders as [Object object]).

[Siyfion]

@chrisirhc It's just nice to know that the issue will be fixed at some point in the future! 👍

[philippd]

@chrisirhc thanks for the update!

[zenix]

Still broken. [Object object] in value of input line

[robianmcd]

@zenix are you using rc.4? That fixed the issue for me