Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: EE-3.2.0.GA, EE-3.3.0.GA
-
Fix Version/s: EE-3.3.0.GA_P01, 4.0.BETA, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:All
-
Assignee Priority:P1
-
Salesforce Case Reference:
Description
Activity
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case Reference | 5007000000Ua4fNAAR |
| Attachment | notificationPanel-tabSet-overlay.jpg [ 16107 ] |
| Assignee | Mark Collette [ mark.collette ] | |
| Fix Version/s | 3.4 [ 10770 ] | |
| Priority | Major [ 3 ] | Minor [ 4 ] |
| Assignee Priority | P1 [ 10010 ] |
| Fix Version/s | EE-3.3.0.GA_P01 [ 11174 ] |
In most cases, giving a z-index of 1 is sufficient to put the notificationPanel on top of everything else, with one of the always showing menu variants, 2 was necessary. But with the menus that popup then 1000 was necessary to show in front of the popup. For autocompleteEntry / comboBox / selectMenu, a value of > 500 is necessary. And with tooltip, a value of 20000 was necessary. But those are all transiently showing things which might make sense to have over top of the notification. When they are behind a notificationPanel, they would be better to detect the notificationPanel as the top of the display and show below in the y axis, then underneath in the z axis. I'm going to go with 10, with the assumption that temporary popups should come in front of the notificationPanel.
Otherwise I would recommend a registration of always present position fixed elements, such as notificationPanel, that popups would use to limit their window sizing and positioning by.
ICEfaces EE 3.3 P01
Subversion 37344
icefaces3 trunk
Subversion 37346
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #37346 | Thu Aug 08 16:09:05 MDT 2013 | mark.collette | |
| Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/ace/component/resources/icefaces.ace/notificationpanel/notificationpanel.css
|
| Fix Version/s | 4.0 [ 11382 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
It's not just that the ace:notificationPanel is shown behind the ace:tabSet, but that it's shown behind the source code ace:panel's header and content areas, with the source code tabSet being inside the source code panel.
And that's not from the source code panel having any special z-index or other layout but simply because the notificationPanel is inside of another ace:panel, that is a something of a peer of the source code ace:panel. As soon as the notificationPanel has a z-index of even just 1, then it shows over the panel header and content areas. A quick search of z-index in the ACE code shows that several components use z-index in the single digits for their regular layout, and several popup/overlay components use z-index of API that searches other z-index values already visible in the page, and dynamically calculates a larger one. Also, adding a z-index property to the notificationPanel would be in line with ace:draggable, but would not be as preferable as dynamic calculation. For a proper hard-coded value, we would need to decide which should display in front, menus or the notificationPanel.