Created attachment 520871 [details]
drift display issue
Description of problem: Drift display issue ... Change Sets-->Context Menu--->Details
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Drift change set, right click context menu, choose details
2. Observe display issue (see attached)
see attached image of display issue
Steps to repro:
-expand Version 0 node
-right-click context menu on the 1st item
-select details from the context menu
-then i see the display issue with the details page, that is documented and attached to this BZ
Conversation from Elluminate session where we reproduced the issue, and documented the additional reproduction steps:
oined on August 31, 2011 at 4:27 PM
jshaughn: I can see your stuff
jshaughn: refresh is slow
Moderator: ok ...here goes ...
Moderator: i clicked on change sets
jshaughn: first, click on Reports
Moderator: let me do my steps ...ok?
jshaughn: not ok
jshaughn: because you're already farther than I want you to be
jhaughn: I belive there is a problem, don't get me wrong
Moderator: we saw the issue ... there it is
jshaughn: I want to ensure that we're seeing the same problem
Moderator: i will now click on reports
Moderator: this is not in my reproduction steps ...so the outcome here is unknown to me
jshaughn: i am not questioning whether there is a problem, I want to ensure there are not two problems
Moderator: i have clicked on reports
Moderator: what is the next thing i need to do
jshaughn: ok, no you can go to favorites, recently viewed or whatever to get back to your platfoirm
jshaughn: not the back button
Moderator: i will stick to the reproduction steps that i have documented
jshaughn: thatis what I'm talking about
Moderator: and the problem does not reproduce after clicking reports
jshaughn: you're repro steps need to be cleaner for this one
jshaughn: that is what I'm saying
jshaughn: because they start once you've already been playing with the drift subtabs
jshaughn: and I had no idea whatyou had already done
jshaughn: anyway, it's ok, I just needed to confirm we were on the same page
jshaughn: you can see it if you now click back to list
Moderator: is state of the UI "dirty" in some way?
Moderator: if the state of the UI is dirty ... then that is another issue
jshaughn: wrt to this bug, yes, the repr steps started in a non-determinsitic state
jshaughn: Now, hit back to list
jshaughn: it's not an issue with anything other than the repro steps
jshaughn: ok, now go ahead and follow your repro steps
Moderator: i have already done that twice
Moderator: once the issue was repro'd
Moderator: and the 2nd time it was not repro'd
jshaughn: try now
Moderator: what are we testing in this 3rd try?
jshaughn: you will see it
jshaughn: because we are now in your original state
Moderator: okay ...
Moderator: so clicking "History": leaves the UI in a dirty state
jshaughn: call it what you want, it's part of the repro steps
jshaughn: ok, thanks, we are now on the same page
This is similar in look to Bug 730065 but its cause is different, and
tricky. Looking into it.
master commit 153c9845c2ac28079b9629b4cc445d7eccca8901
Even if the table view is not visible, it may not be hidden. Instead, it
may be the case that its parent (the encompassing Table/HLayout) may not
be visible. This is unusual because typically we switch between the table
and detail view while under the subtab, but if we navigate to the detail
view from another subtab (for example, the drift tree context
menu) the Table may not be visible and the table view may not be hidden.
To make a long story short, ensure the table view is hidden when
displaying the details view.
verified RHQ 4.1 release candidate.
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE