-
Notifications
You must be signed in to change notification settings - Fork 187
fix(modal): unresponsive app when using both modal and popover #219
Conversation
+1. Cleaner version of the fix I proposed here. Good job! |
Oh, thanks for linking the issue, I had searched and somehow missed it. =) |
Great fix. Why is this fix not merged already? |
It looks like the ionic team completely dropped the support of the v1. They're probably too busy with the v2 (well, it's even v3 now). I suggest you to fork the project and do your own changes/merges.... |
Already did just that. I understand that 1.x is not a priority right now but a bug like this should be fixed, don't you think? |
Yes, I do think. We all do! That's why I created an issue + proposed a fix, and shanesmith created a PR. |
@perrygovier Could you please merge this? Give you some 👏 and will make a 🎉 and eat a 🍰 if you do this. =) |
If someone continues to face this issue after applying the suggested patch and is using angular material along with ionic-v1 you have to add This will prevent firing click multiple times on mobile device (Chrome doesn't seems to be affected, at least on OSX 10.10.5) making the modals pushing themselves multiple times in the |
@jgw96 @perrygovier @mlynch or anyone in the Ionic team to merge this and publish v1 update please? There are various PR waiting for merge, and a suppose a lot of teams waiting for them... Thanks! 👍 |
Short description of what this resolves:
When both a modal and popover are used at the same time there is the possibility of the "modal-open" or "popover-open" body classes not being removed when the modal or popover is hidden. Since these body classes have
pointer-events: none
in their styling the app becomes unresponsive.See comment here: ionic-team/ionic-framework@6ed7253#commitcomment-20105088
Changes proposed in this pull request:
Test only for the modal's viewType in the modalStack when deciding to remove the body class.
Ionic Version: 1.3.2
Fixes: #71