Better story for when a user puts non-ascii characters in client-ui

Bug #956612 reported by Mike Milner on 2012-03-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
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

Revision history for this message
Geoff Teale (tealeg) wrote :

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.

Geoff Teale (tealeg) on 2012-03-26
Changed in landscape-client:
status: New → In Progress
assignee: nobody → Geoff Teale (tealeg)
Geoff Teale (tealeg) on 2012-03-28
Changed in landscape-client:
status: In Progress → Fix Committed
David Britton (dpb) on 2015-04-01
Changed in landscape-client:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers