Skip to content
This repository was archived by the owner on Oct 2, 2019. It is now read-only.

fix(select-choices): Possible fix for #1355 #1518

Closed
wants to merge 2 commits into from

Conversation

dondi
Copy link
Contributor

@dondi dondi commented Mar 23, 2016

...at the cost of potential unnecessary watches when dropdown is closed.
But the premise is that, until the resulting errors are fixed, the
preference is to avoid the errors for now.

Closes #1355

...at the cost of potential unnecessary watches when dropdown is closed.
But the premise is that, until the resulting errors are fixed, the
preference is to avoid the errors for now.

Closes angular-ui#1355
@wesleycho
Copy link
Contributor

This has negative performance implications - it probably would be more ideal to figure out the root cause of the errors.

@dondi
Copy link
Contributor Author

dondi commented Mar 28, 2016

OK; I just send it because it was mentioned as an ad hoc change in the thread for #1355 and users there were generally positive about it. The potential performance impact was a known compromise. I can look harder for the root cause then update the request.

@dondi
Copy link
Contributor Author

dondi commented Apr 18, 2016

Latest upstream source tree appears to remove the original #1355 issue; closing this one.

@dondi dondi closed this Apr 18, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[ui.select:choices] Expected multiple .ui-select-choices-row but got '0'.
2 participants