Bug 771406 - Some table headers not rendering
Summary: Some table headers not rendering
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: John Sanda
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 694221
TreeView+ depends on / blocked
 
Reported: 2012-01-03 16:19 UTC by John Sanda
Modified: 2013-09-01 19:22 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-01 19:22:39 UTC
Embargoed:


Attachments (Terms of Use)

Description John Sanda 2012-01-03 16:19:14 UTC
Description of problem:
In the feature/gwt-upgrade branch, some table headers are not rendering. I have observed this with tables on several different pages including,

* the drift compliance report
* the inventory summary report
* the subsystem reports
* drift definitions view
* the resource metrics table (Monitoring/Tables)

With the inventory summary and drift compliance reports, if I click on one of the resource types, the headers get rendered. And with the drift definitions view, the headers get rendered if I do a page refresh.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 John Sanda 2012-01-03 16:40:27 UTC
I observed this in Firefox 3.6.13, 8.0.1 and in Chrome 10.

Comment 2 John Sanda 2012-01-05 21:12:00 UTC
Fix has been pushed to the feature/gwt-upgrade branch. In Table.java we were adding the ListGrid widget to its parent twice, once in onInit and then again in onDraw. Removing the call to addMember(listGrid) in onInit appears to have resolved the issue.

commit hash: de4e8c75177edc8efab2cfbd6c054b24f10f06a6

Comment 3 John Sanda 2012-02-17 16:44:30 UTC
This has been merged into master.

Comment 4 Heiko W. Rupp 2013-09-01 19:22:39 UTC
Bulk closing of BZs that have no target version set, but which are ON_QA for more than a year and thus are in production for a long time.


Note You need to log in before you can comment on or make changes to this bug.