Better story for when a user puts non-ascii characters in client-ui
Bug #956612 reported by
Mike Milner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Fix Released
|
Medium
|
Geoff Teale | ||
Bug Description
We need a better story to handle invalid (non-ascii) characters in the ui. Ideally an error message should be displayed describing the error so the user can fix it.
Related branches
lp:~tealeg/landscape-client/warn-on-unicode
- Alberto Donato (community): Approve
- Mike Milner (community): Approve
-
Diff: 713 lines (+426/-76)7 files modifiedlandscape/ui/view/configuration.py (+97/-26)
landscape/ui/view/tests/test_configuration.py (+302/-31)
man/landscape-client.1 (+1/-1)
man/landscape-config.1 (+1/-1)
man/landscape-message.1 (+1/-1)
po/fr.po (+12/-8)
po/landscape-client.pot (+12/-8)
Revision history for this message
| Geoff Teale (tealeg) wrote | #1 |
| Changed in landscape-client: | |
| status: | New → In Progress |
| assignee: | nobody → Geoff Teale (tealeg) |
| Changed in landscape-client: | |
| status: | In Progress → Fix Committed |
| Changed in landscape-client: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I would recommend that we use a Gtk.InfoBar (one of those yellow bars that drops down from the top of the window in Firefox, for example) to explain the problem - the Register button would be disabled while this bar is showing, and the action button on the InfoBar would revert the input and enable the Register button again.