Cannot read property `autoHideDropdown` of undefined

[vickramravichandran]

Cannot read property `autoHideDropdown` of undefined

[vickramravichandran]

I was able to reproduce the behavior. The fix after upgrading to 1.7.x is to set "label" to html

	renderItem: item => {
	  return {
	    value: item.name,
	    label: "<span ng-bind='item.name'><span>"
	  }
	},

[vickramravichandran]

Is it possible to create a Fiddle/Codepen for this? I am curious why it does not fail in other places where that.options is accessed.

[andrei-gheorghiu]

Hi Vikram, thank you for the merge.

Update on my situation: while trying to reproduce the issue in a fiddle I wasn't able to anymore. When looking deeper into it, I realized the issue happened on v1.6.4, not on v1.7.2. So, logically, I updated the project dependency to v1.7.3 but it looks like there are breaking changes between v1.6.4 and v1.7.3.

I tried to update our code to work with with v1.7.3 but it looks like it's a no go: I can't seem to find a way to make the input show a label (it shows [object Object]), which in v1.6.4 was achieved by using:

...,
renderItem: item => {
  return {
    value: item.name,
    label: item.name
  }
},...

So, what I ended up doing was: reverted my fork to v1.6.4, applied the lil' fix and installed the package from my fork. If there's any way to achieve the above in latest version, i'd be happy to update.

Thank you.

[vickramravichandran]

Yes, v1.7.0 had major refactoring. I added support for compilation (ng-bind) for the "label". But I did account for backward compatibility. Can you create a simple Plunkr using v1.6.4? I want to see what I broke...

I don't see why label would show [object Object]. See example using renderItem callback on the demo site. See "Custom List Using renderItem Callback".