You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Trevor N. Suarez (Created) (JIRA)" <ji...@apache.org> on 2012/04/20 00:00:41 UTC
[jira] [Created] (CB-549) notification.confirm UX is missaligned
notification.confirm UX is missaligned
--------------------------------------
Key: CB-549
URL: https://issues.apache.org/jira/browse/CB-549
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
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.
http://developer.android.com/design/building-blocks/dialogs.html
"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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-549) notification.confirm UX is missaligned
Posted by "Trevor N. Suarez (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257902#comment-13257902 ]
Trevor N. Suarez commented on CB-549:
-------------------------------------
I'm already using a large split between my min and target: https://github.com/plymouthstate/psu-mobile-native/blob/master/PSU-Mobile-PhoneGap-Android/AndroidManifest.xml#L27
This is tested on Android 2.3, Android 3.0, Android 4.0.2, and iOS 5.1.
An Android 4.0.2 and iOS 5.1 example is included as a screenshot.
> notification.confirm UX is missaligned
> --------------------------------------
>
> Key: CB-549
> URL: https://issues.apache.org/jira/browse/CB-549
> 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.
> http://developer.android.com/design/building-blocks/dialogs.html
> "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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-549) notification.confirm UX is missaligned
Posted by "Joe Bowser (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bowser resolved CB-549.
---------------------------
Resolution: Fixed
Switched the Negative and Positive.
> notification.confirm UX is missaligned
> --------------------------------------
>
> Key: CB-549
> URL: https://issues.apache.org/jira/browse/CB-549
> 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.
> http://developer.android.com/design/building-blocks/dialogs.html
> "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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-549) notification.confirm UX is missaligned
Posted by "Joe Bowser (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bowser updated CB-549:
--------------------------
Fix Version/s: 1.7.0
> notification.confirm UX is missaligned
> --------------------------------------
>
> Key: CB-549
> URL: https://issues.apache.org/jira/browse/CB-549
> 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.
> http://developer.android.com/design/building-blocks/dialogs.html
> "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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CB-549) notification.confirm UX is missaligned
Posted by "Joe Bowser (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bowser reopened CB-549:
---------------------------
There is a difference between confirm and notification.confirm.
> notification.confirm UX is missaligned
> --------------------------------------
>
> Key: CB-549
> URL: https://issues.apache.org/jira/browse/CB-549
> 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.
> http://developer.android.com/design/building-blocks/dialogs.html
> "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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-549) notification.confirm UX is missaligned
Posted by "Joe Bowser (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bowser resolved CB-549.
---------------------------
Resolution: Not A Problem
This is a manifest fix for users who want it.
> notification.confirm UX is missaligned
> --------------------------------------
>
> Key: CB-549
> URL: https://issues.apache.org/jira/browse/CB-549
> 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.
> http://developer.android.com/design/building-blocks/dialogs.html
> "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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-549) notification.confirm UX is missaligned
Posted by "Joe Bowser (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257863#comment-13257863 ]
Joe Bowser commented on CB-549:
-------------------------------
We don't choose where the choices go, we let Android decide that. If you wish to target the latest version of Android (and you don't care about the menu changes), you can add this to your Android Manifest:
{code}
<uses-sdk android:minSdkVersion="5" android:targetSdkVersion="15"/>
{code}
However, please note that this will break any menu plugin or menu setup you're currently using, since Honeycomb and later use ActionBar style menus.
> notification.confirm UX is missaligned
> --------------------------------------
>
> Key: CB-549
> URL: https://issues.apache.org/jira/browse/CB-549
> 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.
> http://developer.android.com/design/building-blocks/dialogs.html
> "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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-549) notification.confirm UX is missaligned
Posted by "Trevor N. Suarez (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257919#comment-13257919 ]
Trevor N. Suarez commented on CB-549:
-------------------------------------
Thank you so much, Joe. I'm quite impressed by the response time. :)
> notification.confirm UX is missaligned
> --------------------------------------
>
> Key: CB-549
> URL: https://issues.apache.org/jira/browse/CB-549
> 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.
> http://developer.android.com/design/building-blocks/dialogs.html
> "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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-549) notification.confirm UX is missaligned
Posted by "Trevor N. Suarez (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trevor N. Suarez updated CB-549:
--------------------------------
Attachment: iOS Confirm.jpg
This is with:
navigator.notification.confirm(
'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: https://issues.apache.org/jira/browse/CB-549
> 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.
> http://developer.android.com/design/building-blocks/dialogs.html
> "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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-549) notification.confirm UX is missaligned
Posted by "Trevor N. Suarez (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trevor N. Suarez updated CB-549:
--------------------------------
Attachment: Android Confirm.jpg
This is with:
navigator.notification.confirm(
'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: https://issues.apache.org/jira/browse/CB-549
> 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
> Attachments: Android 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.
> http://developer.android.com/design/building-blocks/dialogs.html
> "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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira