Ngx-bootstrap: Typeahead throws an exception when no option is selected

Created on 28 Apr 2020 · 8Comments · Source: valor-software/ngx-bootstrap

ERROR TypeError: Cannot read property 'length' of undefined
at TypeaheadDirective.onBlur (ngx-bootstrap-typeahead.js:2010)
at TypeaheadDirective_blur_HostBindingHandler (ngx-bootstrap-typeahead.js:2394)
at executeListenerWithErrorHandling (core.js:21693)
at wrapListenerIn_markDirtyAndPreventDefault (core.js:21742)
at HTMLInputElement. (platform-browser.js:934)
at ZoneDelegate.invokeTask (zone-evergreen.js:399)
at Object.onInvokeTask (core.js:41344)
at ZoneDelegate.invokeTask (zone-evergreen.js:398)
at Zone.runTask (zone-evergreen.js:167)
at ZoneTask.invokeTask [as invoke] (zone-evergreen.js:480)

Source

vindiezel23

👍3 👀1

Most helpful comment

@daniloff200 I'm also experiencing this issue. If you try the Async Data example from the docs pages (Async Example) it occurs there (the stackblitz examples fail to load core-js for me for some reason). To Reproduce:

Place focus in the text field
Do not type anything
Blur the control by going to some other element

In the console you should see the stack trace defined above. In digging a little deeper, the _matches object in onBlur is undefined, thus leading to this error.

batesiiic on 29 Apr 2020

👍8

All 8 comments

hello, @vindiezel23
Could you provide a small demo (Stackblitz) or github repo with your code, when I can reproduce that issue?

That's hard to understand, what's going on here.

I have thoughts, that you doesn't provided a data in model, but, that just a guess

daniloff200 on 28 Apr 2020

Place focus in the text field
Do not type anything
Blur the control by going to some other element

In the console you should see the stack trace defined above. In digging a little deeper, the _matches object in onBlur is undefined, thus leading to this error.

batesiiic on 29 Apr 2020

👍8

@daniloff200 I'm also experiencing the same issue. Exception is being logged in the console when you blur from the input text field without doing anything

anshulckc on 1 May 2020

👍2

I remember that

I didn't experience these issues on a page with a single typeahead Input but
i experienced this on a page with two typeahead inputs.

There have probably been more possible influences in the environment where I tested it. But I am not on a computer right now so I can't create a demo to prove the above described case.