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

Typeahead issues #1988

Closed
vitaly-t opened this issue Mar 26, 2014 · 4 comments
Closed

Typeahead issues #1988

vitaly-t opened this issue Mar 26, 2014 · 4 comments

Comments

@vitaly-t
Copy link

Just looking at the Typehead demo that's on the library's official website, it doesn't seem to work right.

  • Example 1, for "Asynchronous results"
    Type in "Mosc", nothing comes up. Then press "o", suddenly 2 items come up, then "w", for "Moscow", it is found, but strangely, wasn't shown before on the list. That is wrong.
  • Example 2, for "Custom templates for results"
    Type in something and select any item found. Now hit Backspace to remove the last symbol. The select list appears totally out of place.

Tested in Chrome version 33

@pkozlowski-opensource
Copy link
Member

@VitalyTomilov for the first issue - those are the results that we are getting from http://maps.googleapis.com/maps/api/geocode/json so eventual complains should be directed there. But this is just demo API so not really relevant to this directive.

For the second issue - it is a real one, should be fixed.

@bekos
Copy link
Contributor

bekos commented Apr 13, 2014

This is not a typeahead bug. The problem is that the model changes alter the height of the <pre> area. The solution is to either give a standard height on the <pre> element or move it below the typeahead.

@wesleycho
Copy link
Contributor

This does not appear to be issues with typeahead itself.

The second one is a demo site issue, and PRs are welcome fixing it.

@wesleycho
Copy link
Contributor

Closing, as it appears this has been fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants