Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Invalid
-
Affects Version/s: 3.3, 4.1
-
Fix Version/s: EE-4.2.0.GA, EE-3.3.0.GA_P05
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 3.3, ace:dialog and ace:confirmationDialog
-
Assignee Priority:P1
-
ICEsoft Forum Reference:
-
Support Case References:Support Case 14151:- https://icesoft.my.salesforce.com/5007000001kw5z3?srPos=0&srKp=500
Description
An application launches a modal ace:dialog containing an ace:dataTable, which itself has a delete row function.
On delete button click (from the ace:dataTable, inside the modal dialog), the ace:confirmationDialog is displayed but appears under the blocking DIV that the modal ace:dialog renders, making in inaccessible.
The ace:confirmationDialog (and popups in general) that are triggered from inside a modal ace:dialog should appear above/in front of the modal blocking DIV so they remain accessible to the user.
On delete button click (from the ace:dataTable, inside the modal dialog), the ace:confirmationDialog is displayed but appears under the blocking DIV that the modal ace:dialog renders, making in inaccessible.
The ace:confirmationDialog (and popups in general) that are triggered from inside a modal ace:dialog should appear above/in front of the modal blocking DIV so they remain accessible to the user.
Activity
Ken Fyten
created issue -
Ken Fyten
made changes -
Field | Original Value | New Value |
---|---|---|
ICEsoft Forum Reference | http://www.icesoft.org/JForum/posts/list/0/22282.page |
Ken Fyten
made changes -
Assignee | Mircea Toma [ mircea.toma ] | |
Fix Version/s | EE-4.2.0.GA [ 13071 ] | |
Fix Version/s | EE-3.3.0.GA_P05 [ 13082 ] | |
Affects Version/s | 4.1 [ 11375 ] | |
Assignee Priority | P1 [ 10010 ] |
Judy Guglielmin
made changes -
Support Case References | Support Case 14151:- https://icesoft.my.salesforce.com/5007000001kw5z3?srPos=0&srKp=500 |
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Invalid [ 6 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
This is issue seems to be fixed, isn't it?
So, are you trying to find which changes from the past solved this issue?