-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Getting multiple views on the dom. #6711
Comments
Hi, can you please post a reproduction? |
this might be related to some animation changes we made, but we do need a better example in order to reproduce the problem. @matsko do you by chance know what's going on? |
I went straight from 1.2.8 to 1.2.14. I am troubled at how to show more info. My app is roughly 5K lines of code. All I can tell you is that I downgraded back to 1.2.8 and no issues. However as you can imaging it makes it unusable. When you ask for a repro are you talking about jsfiddle/plunker?? I am sure if I grossly simplify my app that it won't happen. All I can tell you is that I have been coding with Angular for about 1year. So I am not new to constructs. My CSS is rather involved. Compiled down from less. I will look at the CSS issue that you reference. To see if it is relevant. |
I don't think the css should be involved in getting duplicate DOM nodes.. ngView uses element transclusion, it's possible/likely that $animate.enter() is getting called twice, or the underlying DOM manipulation is happening twice, without removing the old. It's hard to be sure though, so trying to reproduce would help. I guess it's possible specific css properties are involved, but start with a simple repro first before worrying about that, it should take like 5 minutes |
the css could be causing animations to misfire, which could cause duplicate On Tue Mar 18 2014 at 6:42:56 AM, Caitlin Potter [email protected]
|
@caitp and @IgorMinar it isn't the CSS that is getting involved directly. It's just that We need more info. |
Tell me how to provide more info. I can't turn over my entire code Best, Eric Gould On 3/18/2014 4:44 PM, Matias Niemelä wrote:
|
@emgould it would be best if we pair up on this together. Are you free sometime tomrrow? What timezone are you in and what is your availability? Please email me at the email that is on my github profile. |
I am on the east coast. I could talk in my afternoon around between Best, Eric Gould On 3/18/2014 5:15 PM, Matias Niemelä wrote:
|
Thanks Eric for contacting me. Another related issue popped up about animations and I think I will have a go at this today since the example is easy to understand: #6748. Let me tackle that first and then, if it doesn't solve your issue, let's pair up. Sorry for the change in scheduling. We can save more time by doing it this way. |
@emgould please test this out using these files: Fix fix in the files above fixes #6748 |
@emgould any news? |
Matias, Best, [email protected]
|
@emgould any change you have some time to check this out? |
I can focus on this tomorrow. What would you like me to do? Best, Eric Gould On 4/3/2014 12:15 AM, Matias Niemelä wrote:
|
Please test out your former code using the angular.js files from http://code.angularjs.org/snapshot/ |
Ok. Will let you know. Best, Eric Gould On 4/3/2014 4:50 PM, Matias Niemelä wrote:
|
What was the status of the testing? I am running into this same behavior (in IE9 only). When route changes happen, and ngView attempts to clean out the prior view, IE9 throws an 'Access Denied' error. When I inspect the DOM, I see duplicate ng-view divs. |
@emgould any progress? Can you please try testing using the snapshot version (which is 1.3) there have been a bunch of fixes done to ngAnimate. |
@emgould I'm closing the issue for now. Please reply back here incase you're still experiencing the issue with the latest version of Angular. And please provide a plunkr link to the bug. Thanks. |
matsko I think I can reproduce this issue and put it in this link http://plnkr.co/edit/wm3bcTvdxCdGcWJDXstS?p=preview please let me know your comments |
the problem is that jquery puts the dialog DOM outside ngView div, so every time I navigate to the page with the dialog div it is added to the document again. the solution is to relocate de dialog div inside the ngView div |
Post upgrading to 1.2.14 I am getting multiple views on the dom when I did not previously and it is unexpected. Worked fine previously. My .config looks like the following:
One of many route command might be like this href tag:
If I inspect the dom i see the both the current and past view with the angular animate classes now added:
Very strange...
After some experimentation, I am seeing different behaviors depending upon how the location.path is updated or how the href is specified. I have experimented with href set to: "#/[route]' or location.path('/[route]').
The text was updated successfully, but these errors were encountered: