You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
showCupertinoDialog should support barrierDismissible #45744
In showCupertinoDialog it is not supported to enabled to dismiss the dialog on outside tap. It seems that this might be the normal iOS behaviour, but I couldn't find any documentation that it is not allowed to support it.
Minimize alerts. Alerts disrupt the user experience and should only be used in important situations like confirming purchases and destructive actions (such as deletions), or notifying people about problems. The infrequency of alerts helps ensure that people take them seriously. Ensure that each alert offers critical information and useful choices.
Sounds reasonable to add the parameter but set the default to false.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
alectogeek commentedon Jan 2, 2020
We realy need this feature!
LongCatIsLooong commentedon Jan 2, 2020
I couldn't find anything that says this is not allowed, but from https://developer.apple.com/design/human-interface-guidelines/ios/views/alerts/ it shouldn't be encouraged either, as
barrierDismissible = truemakes it a lot easier for users to dismiss something important by mistake:Sounds reasonable to add the parameter but set the default to false.
tottomotto commentedon Jan 29, 2020
@xster,can you please share your thoughts on this.
I Implemented the change (defaulting to false) and I can make a PR if it's ok.
xster commentedon Feb 4, 2020
Making it configurable (but defaulted to false) seems reasonable to me.
github-actions commentedon Aug 21, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.