| 2013-09-09 12:14:25 |
Matthew Paul Thomas |
bug |
|
|
added bug |
| 2013-09-09 12:15:51 |
Matthew Paul Thomas |
description |
The toolkit does not have a standard error appearance for text fields, other controls, or captions.
The error appearance should be used for fields that you have filled out incorrectly, other controls that have a disallowed state, and captions explaining the problem with individual controls.
Examples:
* If you choose a time in a restaurant reservation system, submit the request, and the server responds that that time is unavailable, the time picker should retain the previous value (so you can see what you chose) but should have the error appearance. A caption should appear below it explaining the problem: for example, “Sorry, 7:30pm is unavailable. Try earlier or later.".
* Similarly, the validity of a checkbox, radio button, switch, etc selection might be too complex or volatile to check on the client side of an app. If the server side responds that the selection isn't allowed, the control should adopt the standard error appearance, and a caption below if necessary.
* Changing the SIM PIN requires entering the current PIN. The phone can't check the correctness of the current PIN with every character you types, because trying an incorrect PIN three times or so will lock the SIM. Instead, it is checked only once you submit the dialog. *Then* if the current PIN turns out to be wrong, that field should get the standard error appearance (maybe a pale pink background, and/or a maroon border, and/or a brief flash), and an explanatory caption below it.
* All the captions mentioned above should have their own consistent error appearance. (Maybe maroon text.) |
The toolkit does not have a standard error appearance for text fields, other controls, or captions.
The error appearance should be used for fields that you have filled out incorrectly, other controls that have a disallowed state, and captions explaining the problem with individual controls.
Examples:
* If you choose a time in a restaurant reservation system, submit the request, and the server responds that that time is unavailable, the time picker should retain the previous value (so you can see what you chose) but should have the error appearance. A caption should appear below it explaining the problem: for example, “Sorry, 7:30pm is unavailable. Try earlier or later.".
* Similarly, the validity of a checkbox, radio button, switch, etc selection might be too complex or volatile to check on the client side of an app. If the server side responds that the selection isn't allowed, the control should adopt the standard error appearance, and a caption below if necessary.
* Changing the SIM PIN requires entering the current PIN. The phone can't check the correctness of the current PIN with every character you type, because trying an incorrect PIN three times or so will lock the SIM. Instead, it is checked only once you submit the dialog. *Then* if the current PIN turns out to be wrong, that field should get the standard error appearance (maybe a pale pink background, and/or a maroon border, and/or a brief flash), and an explanatory caption below it.
* All the captions mentioned above should have their own consistent error appearance. (Maybe maroon text.) |
|
| 2013-09-09 12:18:42 |
Iain Lane |
bug |
|
|
added subscriber Iain Lane |
| 2014-10-01 09:03:20 |
Cris Dywan |
ubuntu-ui-toolkit: status |
New |
Confirmed |
|
| 2014-10-01 09:03:24 |
Cris Dywan |
ubuntu-ui-toolkit: importance |
Undecided |
Low |
|
| 2014-10-01 09:03:43 |
Cris Dywan |
bug task added |
|
ubuntu-ux |
|
| 2014-10-01 12:38:00 |
Giorgio Venturi |
ubuntu-ux: status |
New |
Triaged |
|
| 2014-10-01 12:38:03 |
Giorgio Venturi |
ubuntu-ux: importance |
Undecided |
Medium |
|
| 2014-10-01 12:38:24 |
Giorgio Venturi |
ubuntu-ux: assignee |
|
Olga Kemmet (olga-kemmet) |
|
| 2014-11-24 13:32:16 |
Zoltan Balogh |
ubuntu-ui-toolkit (Ubuntu): importance |
Undecided |
Low |
|
| 2014-11-24 13:32:16 |
Zoltan Balogh |
ubuntu-ui-toolkit (Ubuntu): status |
New |
Confirmed |
|
| 2014-11-24 14:18:11 |
Zoltan Balogh |
bug task deleted |
ubuntu-ui-toolkit |
|
|
| 2014-12-05 12:05:46 |
John Lea |
summary |
No standard error appearance for text fields and other controls |
[SDK] No standard error appearance for text fields and other controls |
|
| 2014-12-05 12:06:00 |
John Lea |
ubuntu-ux: assignee |
Olga Kemmet (olga-kemmet) |
Giorgio Venturi (giorgio-venturi) |
|
| 2015-05-11 16:15:44 |
Magdalena Mirowicz |
ubuntu-ux: assignee |
Giorgio Venturi (giorgio-venturi) |
Olga Kemmet (olga-kemmet) |
|
| 2015-06-29 10:19:04 |
Matthew Paul Thomas |
ubuntu-ux: assignee |
Olga Kemmet (olga-kemmet) |
Jamie Young (jamiedawsonyoung) |
|
| 2015-08-03 10:43:23 |
Jamie Young |
description |
The toolkit does not have a standard error appearance for text fields, other controls, or captions.
The error appearance should be used for fields that you have filled out incorrectly, other controls that have a disallowed state, and captions explaining the problem with individual controls.
Examples:
* If you choose a time in a restaurant reservation system, submit the request, and the server responds that that time is unavailable, the time picker should retain the previous value (so you can see what you chose) but should have the error appearance. A caption should appear below it explaining the problem: for example, “Sorry, 7:30pm is unavailable. Try earlier or later.".
* Similarly, the validity of a checkbox, radio button, switch, etc selection might be too complex or volatile to check on the client side of an app. If the server side responds that the selection isn't allowed, the control should adopt the standard error appearance, and a caption below if necessary.
* Changing the SIM PIN requires entering the current PIN. The phone can't check the correctness of the current PIN with every character you type, because trying an incorrect PIN three times or so will lock the SIM. Instead, it is checked only once you submit the dialog. *Then* if the current PIN turns out to be wrong, that field should get the standard error appearance (maybe a pale pink background, and/or a maroon border, and/or a brief flash), and an explanatory caption below it.
* All the captions mentioned above should have their own consistent error appearance. (Maybe maroon text.) |
[Updated description]
The toolkit does not have a standard error appearance for text fields, other controls, or captions.
The error appearance should be used for fields that you have filled out incorrectly, other controls that have a disallowed state, and captions explaining the problem with individual controls.
Examples:
* If you choose a time in a restaurant reservation system, submit the request, and the server responds that that time is unavailable, the time picker should retain the previous value (so you can see what you chose) but should have the error appearance. A caption should appear below it explaining the problem: for example, “Sorry, 7:30pm is unavailable. Try earlier or later.".
* Similarly, the validity of a checkbox, radio button, switch, etc selection might be too complex or volatile to check on the client side of an app. If the server side responds that the selection isn't allowed, the control should adopt the standard error appearance, and a caption below if necessary.
* Changing the SIM PIN requires entering the current PIN. The phone can't check the correctness of the current PIN with every character you type, because trying an incorrect PIN three times or so will lock the SIM. Instead, it is checked only once you submit the dialog. *Then* if the current PIN turns out to be wrong, that field should get the standard error appearance (maybe a pale pink background, and/or a maroon border, and/or a brief flash), and an explanatory caption below it.
* All the captions mentioned above should have their own consistent error appearance. (Maybe maroon text.)
–––
Desired resolution:
An error state with examples of multiline captions will be added to the SDK UI work underway. |
|
| 2015-08-03 10:43:26 |
Jamie Young |
ubuntu-ux: status |
Triaged |
In Progress |
|
| 2016-03-23 13:54:45 |
Matthew Paul Thomas |
ubuntu-ux: assignee |
Jamie Young (jamiedawsonyoung) |
Femma (femma) |
|
| 2016-05-27 08:27:55 |
Femma |
ubuntu-ux: status |
In Progress |
Fix Committed |
|
| 2016-05-27 08:28:38 |
Femma |
description |
[Updated description]
The toolkit does not have a standard error appearance for text fields, other controls, or captions.
The error appearance should be used for fields that you have filled out incorrectly, other controls that have a disallowed state, and captions explaining the problem with individual controls.
Examples:
* If you choose a time in a restaurant reservation system, submit the request, and the server responds that that time is unavailable, the time picker should retain the previous value (so you can see what you chose) but should have the error appearance. A caption should appear below it explaining the problem: for example, “Sorry, 7:30pm is unavailable. Try earlier or later.".
* Similarly, the validity of a checkbox, radio button, switch, etc selection might be too complex or volatile to check on the client side of an app. If the server side responds that the selection isn't allowed, the control should adopt the standard error appearance, and a caption below if necessary.
* Changing the SIM PIN requires entering the current PIN. The phone can't check the correctness of the current PIN with every character you type, because trying an incorrect PIN three times or so will lock the SIM. Instead, it is checked only once you submit the dialog. *Then* if the current PIN turns out to be wrong, that field should get the standard error appearance (maybe a pale pink background, and/or a maroon border, and/or a brief flash), and an explanatory caption below it.
* All the captions mentioned above should have their own consistent error appearance. (Maybe maroon text.)
–––
Desired resolution:
An error state with examples of multiline captions will be added to the SDK UI work underway. |
[Updated description]
The toolkit does not have a standard error appearance for text fields, other controls, or captions.
The error appearance should be used for fields that you have filled out incorrectly, other controls that have a disallowed state, and captions explaining the problem with individual controls.
Examples:
* If you choose a time in a restaurant reservation system, submit the request, and the server responds that that time is unavailable, the time picker should retain the previous value (so you can see what you chose) but should have the error appearance. A caption should appear below it explaining the problem: for example, “Sorry, 7:30pm is unavailable. Try earlier or later.".
* Similarly, the validity of a checkbox, radio button, switch, etc selection might be too complex or volatile to check on the client side of an app. If the server side responds that the selection isn't allowed, the control should adopt the standard error appearance, and a caption below if necessary.
* Changing the SIM PIN requires entering the current PIN. The phone can't check the correctness of the current PIN with every character you type, because trying an incorrect PIN three times or so will lock the SIM. Instead, it is checked only once you submit the dialog. *Then* if the current PIN turns out to be wrong, that field should get the standard error appearance (maybe a pale pink background, and/or a maroon border, and/or a brief flash), and an explanatory caption below it.
* All the captions mentioned above should have their own consistent error appearance. (Maybe maroon text.)
–––
Desired resolution:
An error state with examples of multiline captions will be added to the SDK UI work underway.
UX fix:
Error handling pattern can be found on in this document: https://docs.google.com/document/d/1rUsPorlYkeetQNYyFWn74mtOY2L4Us53Zx9XujRTPCM/edit |
|
| 2016-05-31 15:15:32 |
Matthew Paul Thomas |
ubuntu-ux: status |
Fix Committed |
Confirmed |
|
| 2016-06-10 10:15:21 |
Femma |
ubuntu-ux: status |
Confirmed |
Fix Committed |
|
| 2016-06-10 10:15:28 |
Femma |
ubuntu-ui-toolkit (Ubuntu): status |
Confirmed |
Fix Committed |
|
