-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Changing data bound to Ember.Select doesn't update selection #481
Comments
Your example helped me immensely, so maybe I can pay back... I had a very similar problem, but related to restoring Select(ed) values from persistance - the Selects wouldn't update. The following code doesn't seem to have any effect in your jsfiddle example, but I'm not a jsfiddle user yet, so maybe I'm not using it correctly. The basic idea is that your user property DOES have the data, but the groups property no longer points to the group set at initialization as far as the Select is concerned. So you get the id of the group, get the associated group instance from xxxGroups, ans set that into user.group. This will also trigger the change event for the Select so that it refreshes....I think. |
Per RFC #481, we want to align the factory signature between templates and component managers. Since the factories for component managers are just a function that takes the owner, we decided to move template factories in the same direction here as well. Co-authored-by: Robert Jackson <[email protected]>
Per RFC #481, we want to align the factory signature between templates and component managers. Since the factories for component managers are just a function that takes the owner, we decided to move template factories in the same direction here as well. Co-authored-by: Robert Jackson <[email protected]>
Per RFC #481, we want to align the factory signature between templates and component managers. Since the factories for component managers are just a function that takes the owner, we decided to move template factories in the same direction here as well. Co-authored-by: Robert Jackson <[email protected]>
Per RFC #481, we want to align the factory signature between templates and component managers. Since the factories for component managers are just a function that takes the owner, we decided to move template factories in the same direction here as well. Co-authored-by: Robert Jackson <[email protected]>
…_return_with_rfc [RFC #481] change return of getComponentTemplate from null to undefined to align with RFC
…rn/ember/jquery-1.1.0
First of all, here's a jsfiddle that demonstrates the problem:
http://jsfiddle.net/KPXYd/4/
When the data behind the Select view changes, the options are correctly updated, but the new selected item is not selected. When stepping through the code, it seemed to me that the following happens:
selectionBinding
is updated first and the new selection gets highlighted (possibly on the oldcontent
?)contentBinding
is updated next, and thus the options get re-rendered and the highlighted selection gets 'lost'.I'm not sure if the above is actually the cause. Maybe someone else can look into it.
The text was updated successfully, but these errors were encountered: