Bug 149508
Summary: | Navigation tree expands unexpectedly | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Paul Kennedy <pkennedy> |
Component: | redhat-config-cluster | Assignee: | Jim Parsons <jparsons> |
Status: | CLOSED DEFERRED | QA Contact: | Cluster QE <mspqa-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4 | CC: | adstrong, cluster-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-28 15:55:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Paul Kennedy
2005-02-23 18:00:15 UTC
will fix This was a complicated fix! Much more involved than immediately thought. Fixed in 0.9.17-1.0 Partially fixed. Now only the tree which was changed expands. So if you close the nodes section, and then add a new node, that tree expands when it should stay the way it was. The user can open it if they want. Actually, I did this purposefully so that the user would have immediate feedback that the node they had added was present in the config. Leaving that section closed would not provide any immediate evidence that the operation was usccessful. If, after reading this explanation, you still feel it should remain closed, then please reset this bug to assigned again. :) We still really think that if the user went to the trouble to close the tree then it should stay that way. They could have left it open when creating the new node or opened it afterwards if they want feed back. This late in the game I'll close it deferred and argue again for it in the uber GUI. :) |