GNOME Bugzilla – Bug 555574
[nm-connection-editor] inform when a value of a field is wrong
Last modified: 2020-11-12 14:34:13 UTC
in nm-connection-editor, when the value of one field is wrong in connection, the button "Okay" stay unsensitive for unknown reason from the user point of view (I only noticed nm-c-e wasn't happy with the values once I run it from terminal), and it obliges to close the window without saving their change. This is a usability problem. Something (like a small icon beside the field) should inform the user the value is wrong.
yeah. as a first step we could display a "warning" next to the field. Later we could add a summary on what is wrong in tooltip of that warning icon or even in a "yellow" bar that appears at the bottom (or top) of the editor page.
(In reply to comment #1) > yeah. as a first step we could display a "warning" next to the field. Later we > could add a summary on what is wrong in tooltip of that warning icon or even in > a "yellow" bar that appears at the bottom (or top) of the editor page. Yep, this is basically what I was envisioning. I updated the nm_connection_verify() error stuff for specifically this purpose, each setting will return the property name of the value that fails verification. We should be able to match that up with the UI widget and a message at some point.
I don't know if Gtk+ provide something like SexyIconEntry (http://www.chipx86.com/w/index.php/Libsexy#SexyIconEntry), but this is what thinking
SexyIconEntry icon functionality is integrated in GtkEntry since GTK+ 2.16. See http://library.gnome.org/devel/gtk/unstable/gtk-migrating-entry-icons.html and http://live.gnome.org/GnomeGoals/DropLibsexy for more info
thanks. sounds like a reasonable approach to display the warnings inline. I think 2.16 should be ok for trunk as we cannot really backport easily because of things like policykit and udev etc.
Note also, that when the "Save"/"Create" button is disabled, you now see a tooltip showing the reason. That kinda fixes this bug, but design wise it's not nice because it's hard to find.
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).