Skip to content

Couple UX improvements#8

Open
avargaskun wants to merge 4 commits into
Paldom:masterfrom
avargaskun:master
Open

Couple UX improvements#8
avargaskun wants to merge 4 commits into
Paldom:masterfrom
avargaskun:master

Conversation

@avargaskun

Copy link
Copy Markdown

iOS

  • Wait until dialog is dismissed before sending result back to Cordova app. Without this, certain UI elements that are shown as part of the callback end up being hidden along with the dialog as it gets closed by the OS.

Android

  • Request focus on the text-editor field in the dialog, which brings up the soft-keyboard after opening the dialog. iOS already behaves this way (no fix needed)

avargaskun and others added 4 commits December 29, 2020 14:18
- On iOS the keyboard is displayed automatically when the dialog is shown
- This change makes it work the same way on Android
- Do not callback into the Cordova application until dialog is dismissed
- Otherwise, UI elements shown after the callback get dismissed along with the dialog
UIAlertView is deprecated and, on the cordova-ios 8 UIScene lifecycle,
instantiating it throws NSObjectNotAvailableException -> SIGABRT. Rewrite
prompt: with UIAlertController, preserving the exact JS contract
(1-based buttonIndex by position, input1, success-only result). Drop the
UIAlertViewDelegate conformance and delete the old delegate callback.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The action handlers captured the alert strongly to read its text field,
forming an alert->action->handler->alert cycle that leaked one controller
per prompt. Capture the alert weakly instead.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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

Successfully merging this pull request may close these issues.

1 participant