All of my modals seemed to have stopped working after an upgrade from .19 -> .22. I had a look at the docs and didn’t notice any interface changes. No errors in my logs/console etc. I looked through recent ionic commits but nothing has changed in ionicModal in the last 3 weeks.
The modal is attached to the DOM properly and all the rules/computed styles seem to be correct. The modal has the proper height, width, position, opacity etc. but simply isn’t visible on the screen. Tried playing with the z-index but that doesn’t seem to be the problem.
One thing I am noticing that is a little odd is that each time I return to a ui-router state with a controller that instantiates a modal, a new modal is create and attached to the dom. So after navigating to a specific page 3 times, I’ll have three instances of my modal on the DOM. Wondering if I should have some clean-up code somewhere to take care of this or if this was intended to be managed by the ionic framework.
Thanks for the response dexlo. The change to ionic modal that you’re referring to was one of the changes I mentioned that happened 3 weeks ago. We made that change around that time and have been using $ionicModal since.
After some git bisect-ing I’ve determined that our upgrade to 0.9.22 was definitely the change that broke our app. We skipped 0.9.21 in the upgrade so I decided to give that version a try and I verified that our app does work properly with 0.9.21.
EDIT: Unfortunately, ng-click seems to suffer from some issues in 0.9.21 so that isn’t an option for us right now either.
Actually, @gavares, would you be able to try the nightly build? (sorry to throw so many versions at you). I recently made another fix to the tap/click: http://code.ionicframework.com/#nightly