Created attachment 436003 [details]
Create fence device dialog that displays the issue
Description of problem:
It is standard practice for drop-down menus to remember their selection.
For some reason the ones in the GUI do not leading the user to question if there was a problem with the selection.
Definitely not at all serious, just a minor visual annoyance.
Attachment shows indicated behavior.
Version-Release number of selected component (if applicable):
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
This should be fixed as of http://git.fedorahosted.org/git/?p=luci.git;a=commit;h=07c8cd29234f474e853cf6d4f56e746ef57da31a
GUI parts affected (and tested):
* certain cluster - fence devices - add
* certain cluster - nodes - certain node - add a fence method - add a fence instance
* certain cluster - resources - add
* certain cluster - services - add - add a resource/add a child resource (but this is a bit different case)
Under the line:
There is still an extremely minor bug (does not affect usability at all) I found by chance and maybe it resides in jQuery framework or even in Firefox:
1/ open a dialog with drop-down menu mentioned above
2/ start choosing from drop-down menu, navigate the cursor above certain (selectable) item, it should be highlighted now
3/ do not click on it, but do a double-click somewhere else within the the dialog
-> it does action like the highlighted item was really selected, but the selector itself is unchanged (strange)
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.