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

Create GwtTestCase on the branch "typeahead-free-text" #30

Closed
gabor-farkas opened this issue Oct 22, 2014 · 0 comments
Closed

Create GwtTestCase on the branch "typeahead-free-text" #30

gabor-farkas opened this issue Oct 22, 2014 · 0 comments
Assignees

Comments

@gabor-farkas
Copy link

The expected behaviour:
If the Typeahead allows custom test, it's always bound as String, with bindCustomText. This however doesn't affect the selectable options of the typeahead, they can still be of any type. So if the user selects a suggested value, if will be written to the presenter with the propert type. If the user enters a custom text, it will be bound to another presenter property with String type.

Things to test (allowing custom text):

  • if a suggested value is selected, it's reflected in the target bound with typeahead.bind() (from abstractselect), and the custom text (the target of bindCustomText) is null.
  • if a custom text is entered, the value will be null on the presenter (the selectedindex is -1 in the model), and the custom text has the user entered value.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants