incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trevor N. Suarez (Updated) (JIRA)" <>
Subject [jira] [Updated] (CB-549) notification.confirm UX is missaligned
Date Thu, 19 Apr 2012 22:22:39 GMT


Trevor N. Suarez updated CB-549:

    Attachment: iOS Confirm.jpg

This is with:

	'Add as a contact?',  // Message
	confirmChoice,                               // Function to parse choice
	'Add Contact?',                              // Title
	'No,Yes'                                     // Choices
> notification.confirm UX is missaligned
> --------------------------------------
>                 Key: CB-549
>                 URL:
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 1.6.1
>         Environment: Android 3.0 and above
> Android 2.3 and below
>            Reporter: Trevor N. Suarez
>            Assignee: Joe Bowser
>            Priority: Minor
>              Labels: android, confirm, ios, notification, ux
>             Fix For: 1.7.0
>         Attachments: Android Confirm.jpg, iOS Confirm.jpg
> The notification.confirm() function places the options in the wrong order.
> iOS and Android 3.0+ should always use the dismissive action on the left and the confirming
action on the right. Android 2.3 and below used the UX paradigm of having those orders reversed.
> Right now, if one were to set the buttons as 'No,Yes', then iOS would show the correct
order, but Android 3.0+ has the buttons backwards, as the confirmation API uses the older
Android 2.3 and below style. However, either way the Android implementation is backwards.
The Android 2.3 button order should NOT match up with iOS like it currently is. And the Android
3.0+ order should be the same as iOS.
> "As a rule, the dismissive action of a dialog is always on the left whereas the affirmative
actions are on the right."

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message