You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 8, 2019. It is now read-only.
It's the first time I use backbone-support to handle zombie views.
Before introducing it, I did not have the following problem:
this.$el.append(this.template());
// this view fills up a select with options taken from a web services
this.renderChildInto(new App.view.ResourcesView({name: "idActivityDesc", url: "/wfc-services/resources/activities"}), "#divIdActivityDesc");
// population of the forms elements according to the loaded model
this.populateSelectElements();
this.populateTextElements();
if(this.model.get('completed')) {
this.$("#active").removeAttr("disabled");
}
this.delegateEvents(this.events);
return this;
With Firefox it's all working fine. If the model is empty the select elements are going to be set up with default elements. In my case is selectedIndex to -1.
Going in debug inside the view everything seems fine. I have the problem when the view is going to be happened to the parent via the method renderChildInto. The dom is fine, but without the changes derived from the populateSelectElements() if the model is empty. If it's not empty I have no problem and the view is working fine.
I'm really puzzled about it because before the return this; statement, even in Chrome/Chromium I see the selectedIndex to -1. But in the final rendered view on the browser I see the select having selectedIndex to 0.
@invasionofsmallcubes Are you still experiencing this problem? Were you able to find a solution? If not, could you provide a gist or sample code that reproduces the problem?
It's the first time I use backbone-support to handle zombie views.
Before introducing it, I did not have the following problem:
With Firefox it's all working fine. If the model is empty the
select
elements are going to be set up with default elements. In my case is selectedIndex to -1.Going in debug inside the view everything seems fine. I have the problem when the view is going to be happened to the parent via the method
renderChildInto
. The dom is fine, but without the changes derived from thepopulateSelectElements()
if the model is empty. If it's not empty I have no problem and the view is working fine.I'm really puzzled about it because before the
return this;
statement, even in Chrome/Chromium I see the selectedIndex to -1. But in the final rendered view on the browser I see the select having selectedIndex to 0.In the composite_view.js the called code is:
The text was updated successfully, but these errors were encountered: