ng-repeat breaks collapsing about angular-material-sidemenu

[gmanriqueUy]

@andersonfalcao ping

[andersonfalcao]

@gmanriqueUy I'll see this question for you! Thanks for reporting this bug

[gmanriqueUy]

@andersonfalcao thank you!

[prabodh44]

I have the same issue, I would love to see this fixed asap.

[andersonfalcao]

@gmanriqueUy and @prabodh44 I'm looked this problem here! Can you tell me what the browser do you use and the browser version.

Do you use the angular side menu last version ? Because I heven't the problem! You can see this at the plunkr

I'm waiting for the answer for I can to finish the issue :)

[prabodh44]

I am currently using Chrome Version 63.0.3239.132. I have been using the angular-material-sidemenu that I have downloaded from npm. The version of angular-material-sidemenu is 1.0.6

[gmanriqueUy]

I'm using version 1.0.6 of this package; same as the plunkr linked in the first comment.

[andersonfalcao]

@prabodh44 @gmanriqueUy Did you tested my Plunkr? if you say yes, did work well?

[gmanriqueUy]

I tested it and it works fine, yes. Which version is that plunkr using?

[andersonfalcao]

@gmanriqueUy I'm using the last version of Github on Master branch!!!!

Any problem tell me and I help you :)

Your feedback is excellent! Thank you

[prabodh44]

Yes i have also tested your plunker. It is working fine as well. thank you

[victormaneac]

It would also help a lot if you could provide more info about what differs between the 2 versions from Plunkr. I have also the same problem and it is not very clear at the moment which was/is the issue.

Note: I have used the bower install angular-material-sidemenu command in order to install it.

[victormaneac]

After some digging, it seems that the issue is in the CSS file, although there are some code differences between the JS files (I mean, between the one from git and the one from Plunkr).

I have replaced the JS and CSS content that I had installed via bower with the ones from @andersonfalcao's example - plunkr - and everything went smoothly :)

@andersonfalcao - shouldn't this issue be closed (after modifying the code also in the repo) ?