Bug 724445 (BRMS-390) - Web decision table: Apply button appends new set of 3 div elements to the page body each time it is clicked
Summary: Web decision table: Apply button appends new set of 3 div elements to the pag...
Keywords:
Status: CLOSED WONTFIX
Alias: BRMS-390
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: 5.1.0.ER2
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-15 11:48 UTC by Jiri Locker
Modified: 2010-11-05 10:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-05 10:32:10 UTC
Type: Bug

Attachments (Terms of Use)
WDT_Apply.png (164.89 KB, image/png)
2010-10-15 11:51 UTC, Jiri Locker 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-390 0 None None None Never

Description Jiri Locker 2010-10-15 11:48:28 UTC 
Steps to Reproduce: 1. create new / open existing Web Decision Table
2. access the (options) section and click Apply
securitylevel_name: Public

I would expect the same "element re-usage" approach as with the message boxes, that appear form time to time ("Loading asset...", "Please wait, saving..." and that kind).
Comment 1 Jiri Locker 2010-10-15 11:51:51 UTC 
Attachment: Added: WDT_Apply.png
Comment 2 Tihomir Surdilovic 2010-10-26 15:38:43 UTC 
Looked at this for quite some time and it turns out that this is typical behavior of the underlying grid gwt component. the divs are added each time and later on used for drag/drop of the columns. Don't think this is a very serious issue in order to deal with it now (unless we get a serious customer request later).
Comment 3 Tihomir Surdilovic 2010-10-26 15:39:20 UTC 
won't fix as its standard gwt behavior
Note You need to log in before you can comment on or make changes to this bug.