Bug 809617
| Summary: | Configuration editor issues with set/unset, drop down lists, and map of simples | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Simeon Pinder <spinder> | ||||
| Component: | Core UI | Assignee: | Jay Shaughnessy <jshaughn> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.3 | CC: | hrupp, jshaughn | ||||
| Target Milestone: | --- | ||||||
| Target Release: | RHQ 4.4.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-09-01 10:14:55 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 735475 | ||||||
| Attachments: |
|
||||||
|
Description
Simeon Pinder
2012-04-03 20:00:19 UTC
Created attachment 574981 [details]
empty drop down list after clear.
This is super annoying. It really has nothing to do with operations, it's just the standard ConfigurationEditor component. The main issue is that SmartGWT is calling the BlurHandler when you expand the SelectItem choices. Looking at alternatives to improve the behavior without borking other stuff. We might want to raise the priority and severity of this bug a little. The issue is even worse for lists/dropdowns for which no values are initially set. In that case the drop down lists show up as disabled, as one would expect, but there is not way to even see possible/available values because the list is unset to begin with. In that case the initial workaround will not help and restarting a scheduled operation just returns you to the same incorrectly blank lists. I was already working on it, I'm offended :-) Anyway, I changed the title of this to reflect that this does not have to do with operation configs but rather the config editor in general. Given the general nature of the problems I upped the priority/severity to high/medium. master commit 61448016c00bb9b2c75165808d5ce4ee221bbc68 When editing a config "unset" should disable the field and nullify the value. When setting (unchecking the "unset" checkbox) the field should be enabled and focus should be given to the field. If navigating away without setting a value the field should automatically be unset. Behavior should be consistent when toggling "unset" whether it is for the current field or a different field. There have issues with this behavior going back to the beginnings of the new gui impl. The scenario in this BZ is a particular bad example. Also, the upgrade to smartgwt 3.0 seems to have affected things a bit negatively as well. This fixes many of these issues, although given the complexity of the component I'd be surprised if it fixed them all. Additionally, the "Delete" SelectItem for a Map of Simples was no longer properly displaying the values after the upgrade. I've solved this although it's maybe not super visually pleasing (but unless there is a complaint I'm not going to spend any more time dorking with it). Test Notes: One of the best ways to test config editor behavior is to navigate to #Test (manually type in this anchor). From there you can access various config editor test views. Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since. |