Container Release Notes *** version 2.4.1 *** No change *** version 2.4.0 *** Fixed the following bugs: ------------------------- + constraintoviewport and fixedcenter now handle Overlays which are larger than the viewport. The Overlay will be positioned such that it's top, left corner is in the viewport. Panel's draggable behavior now also honors constraintoviewport, if the panel is larger than the viewport. + constrainToViewport will now correctly constrain Overlays which haven't been specifically positioned (don't have an XY value set). + Overlay/OverlayManager bringToTop methods will bring Overlays to the top of the stack, even if their current zindex is the same as other Overlays on the page. + Fixed double textResizeEvents fired on gecko based browsers (e.g Firefox 2.x). + Panel underlay now resizes correctly in Safari 2.x, when the content of the Panel is modified (e.g. when setBody() is called). + Tooltip "text" configuration property is no longer overridden by the "title" attribute value on the context element if both are set. The "text" configuration property takes precedence (as indicated in the Tooltip documentation). + Transparent shadows no longer become opaque (black) in IE6/IE7 when a Panel with ContainerEffect.FADE is hidden and then shown again. Also on IE6/IE7 transparent shadows no longer appear opaque while animation is in progress. + An empty header is no longer created for non-draggable Dialogs/SimpleDialogs which don't provide their own headers. By design, an empty header is still created for draggable Dialogs/SimpleDialogs which don't provide a header, in order to provide a drag handle. + Select boxes inside Modal Panels on IE6 are no longer hidden. + In Sam Skin, Dialog/SimpleDialog default and non-default HTML buttons (used when YUI Button is not included on the page) now have a consistent look. Previously style properties intended for default YUI Buttons, were being incorrectly applied to default HTML buttons, giving them a look inconsistent with non-default buttons. Added the following features: ----------------------------- + Added "dragOnly" configuration property to Panel, to leverage the "dragOnly" configuration property added to the DragDrop utility for 2.4.0. When the "dragOnly" configuration property is set to true, the DD instance created for the Panel will not check for drop targets on the page, improving performance during drag operations which don't require drop target interaction. The property is set to "false" by default to maintain backwards compatibility with older 2.x releases, but should be set to "true" if no drop targets for the Panel exist on the page. See the DragDrop utilities 2.4.0 README for additional information. *** version 2.3.1 *** Fixed the following bugs: ------------------------- + To help reduce the occurrence of "Operation Aborted" errors in IE, containers which are rendered to the document's BODY element (e.g. myOverlay.render(document.body)) are now inserted before the first child of the BODY element. This applies to both the container element as well as the iframe shim if enabled. Prior to 2.3.1, these two elements were appended as the last children of the BODY element. When rendering to any other element on the page, the behavior is unchanged and both the container and shim are appended as the last children of the element. Upgrade Impact For Containers Rendered To Document.Body ------------------------------------------------------- If you have an xy coordinate and non-zero z-index specified for your container there should be no negative impact. If you haven't specified an xy position, the fix could result in a shift in your container position, depending on other elements on the page. If you haven't specified a z-index and are relying on DOM order to stack the container, you may see a change in stacking order of the container or iframe shim. Both these changes can be resolved by setting a specific z-index and position based on the layout of other elements on your page. If you do need to revert to 2.3.0 behavior, a configuration property "appendtodocumentbody" has been added to Module, which can be set to true. The change to stacking order is discussed in detail below in relation to other z-index fixes made for 2.3.1. + Z-index is now applied correctly for Overlay/Panel elements, their corresponding iframe shims, and modal masks (for Panels). This fix applies to both the default z-index based on the CSS for the Overlay/Panel and specific z-indices set using the "zindex" configuration parameter. Default z-index values are: Overlay/Panel element: 2 Iframe shim: 1 Mask: 1 The iframe shim and modal mask z-index will always be set to one less than the Overlay/Panel z-index. PLEASE NOTE: As a result of the fix to reduce "Operation Aborted" errors, setting a z-index of 1 on an Overlay/Panel rendered to document.body will result in its iframe shim and modal mask (which will have a z-index of 0) being rendered behind other positioned elements in the document. This is because the Overlay/Panel, iframe shim and mask are inserted as the first children of the BODY element and hence any positioned elements with a z-index of 0 or auto which occur after them in the document will be stacked on top of them as per W3C spec. If you need to keep the Overlay/Panel above positioned elements on your page, it's z-index needs to be set to 2 or more. In general it's advisable to manage the z-index of positioned elements on your page deliberately by setting a z-index, to avoid having their order in the document define their stacking order. For detailed stacking order information see: - http://www.w3.org/TR/CSS21/visuren.html#layers - http://developer.mozilla.org/en/docs/Understanding_CSS_z-index:The_st acking_context + Module now correctly recognizes standard module header, body and footer DIVs when they have extra CSS classes applied in addition to the required hd, bd, and ft classes. e.g.
. + An empty header (set to $#160;) is created for draggable Panels which don't have a header specified, to provide a drag handle. This fixes a regression introduced in 2.3.0 so that 2.2.2 behavior is restored. + Dialog.destroy has been fixed to account for Dialog form elements which may not be direct children of the standard module body ("bd") element. + SimpleDialog.destory now completes successfully if the optional button-beta.js dependancy is not included on the page. + Destroying Overlays registered with the OverlayManager no longer results in a JavaScript error. The Overlay is destroyed and removed from the OverlayManager correctly. + Submitting a Dialog form directly (e.g. using a "submit" button, hitting enter on a single text field form) no longer throws a JavaScript error. Known Issues ------------ + IE: Borders for tables with border-collapse:collapse remain visible ------------------------------------------------------------------- If an Overlay, or any of its subclasses, contains a table with its border-collapse CSS property set to "collapse" instead of the default value of "separate", the borders of the table will remain visible, when the Overlay is configured to be hidden initially. The table contents will be hidden correctly. This is due to an IE bug, reproducible by the basic test case below:1 | 2 |