Bug 1004768 - Multiple Dropdowns in the listbar doesn't work
Summary: Multiple Dropdowns in the listbar doesn't work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER4
: 6.0.0
Assignee: Alexandre Porcelli
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-05 12:54 UTC by Mauricio Salatino
Modified: 2016-08-01 01:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:09:58 UTC
Type: Bug


Attachments (Terms of Use)
both dropdowns pressed, when just one was clicked (57.76 KB, image/png)
2013-09-05 12:57 UTC, Mauricio Salatino
no flags Details

Description Mauricio Salatino 2013-09-05 12:54:55 UTC
Description of problem:
When a list bar contain more than one dropdown (menu with items) just one of them work, no matter which one you click, the same is always opened. 

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


How reproducible:
Go to the ProcessInstanceDetails screen and click Actions or Views
Those menues are defined here: https://github.com/droolsjbpm/jbpm-console-ng/blob/master/jbpm-console-ng-process-runtime/jbpm-console-ng-process-runtime-client/src/main/java/org/jbpm/console/ng/pr/client/editors/instance/details/ProcessInstanceDetailsPresenter.java#L273

I'm attaching a screenshot that shows both dropdowns pressed but just one opened


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Mauricio Salatino 2013-09-05 12:57:21 UTC
Created attachment 794268 [details]
both dropdowns pressed, when just one was clicked

Comment 3 Alexandre Porcelli 2013-09-12 13:54:23 UTC
Fix pushed to UberFire on master and 0.3.x branches

https://github.com/droolsjbpm/uberfire/commit/00c9bd736
https://github.com/droolsjbpm/uberfire/commit/e10abb599


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