Bug 689951 - A newly created Message Center Window doesn't accept row selection/double click
Summary: A newly created Message Center Window doesn't accept row selection/double click
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.0.Beta1
Hardware: Unspecified
OS: Unspecified
high
low vote
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq4
TreeView+ depends on / blocked
 
Reported: 2011-03-22 20:44 UTC by John Mazzitelli
Modified: 2011-05-24 01:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-24 01:08:37 UTC


Attachments (Terms of Use)

Description John Mazzitelli 2011-03-22 20:44:41 UTC
1) Start the GUI fresh (open a new browser tab)
2) Get a message to be posted (change a config, import something, whatever)
3) Click Message Center button to show the message center window
4) Try to double click a message to see its details, notice you can't select a row

Workaround - click the Refresh button. Now the list grid accepts selections/double clicks.

For some reason, when the Message Center View is first created, the list grid does not allow you to select a row or double click a row. But after you refresh the table, it starts working.

Comment 1 John Mazzitelli 2011-03-24 01:37:29 UTC
commit 7f51c8b - needed to add a markForRefresh when the window was initially created and shown. this is now fixed and you can select the rows in the message center table when the window is first created/popped up

Comment 2 Sunil Kondkar 2011-04-29 10:22:16 UTC
Verified on build#39 (Version: 4.0.0-SNAPSHOT Build Number: 15a53e5)

User is able to select and double click the row in the message center window when it is first created. After double click, it displays the details of the message.

Marking as verified

Comment 3 Corey Welton 2011-05-24 01:08:37 UTC
Bookkeeping - closing bug - fixed in recent release.


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