Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with FBDialog #32

Open
guidev opened this issue Aug 21, 2012 · 5 comments
Open

Problem with FBDialog #32

guidev opened this issue Aug 21, 2012 · 5 comments

Comments

@guidev
Copy link

guidev commented Aug 21, 2012

When a FBDialog view is displayed by pressing a button in the actionsheet, the actionsheet does not dismiss correctly: the UI does not respond to touches.

@iosware
Copy link

iosware commented Oct 4, 2012

Can observe the same problem - I can tap through BlockAlert or BlockActionSheet and can't close/dismiss them.

@barrettj
Copy link
Collaborator

This may have been fixed by a previous commit, let me know if there are still issues as I don't use FBDialog.

@BenMoment
Copy link

This issue should stay open as I confirm it still persists. It's also fairly easy to reproduce. If you open a FBDialog from the alert's button block, the alert is dismissed (animation wise) but the screen is still dimmed and locked (UI unresponsive)

@barrettj barrettj reopened this Jun 4, 2013
@barrettj
Copy link
Collaborator

barrettj commented Jun 4, 2013

Reopened; but as none of the maintainers use FBDialog a fix from one of us is unlikely. We'll gladly welcome a pull--request that fixes the issue.

@giffnyc
Copy link

giffnyc commented Aug 27, 2013

A pull request was submitted. The issue appears to be that the FBDialog class makes itself a child of the UIApplication.keywindow. When called within a blockaction, this FBDIalog view remains within the BlockBackground view hierarchy, and prevents the view from resigning its role as keywindow. The fix moves such views into the previous keywindow so that it can be restored.

This was a quicky fix - @Barretj and others are probably more qualified than I to asses unintended consequences of this fix. But it works in my app tests.

Pull Request #62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants