Threaded View
-
9 Mar 2012 8:58 AM #1
Message box styling issue in IE only
Message box styling issue in IE only
REQUIRED INFORMATIONExt version tested:
- Ext 4.0.7
- IE8/compatibility mode
- Styling issue with message box in IE
- Added ext code below to examples/theme/theme.js
- Set up custom theme using the steps listed in learning guide
- Added one custom line(white background listed below)
- correct styling
- buttons overlap background
HELPFUL INFORMATIONScreenshot or Video:Debugging already done:Code:var dialog = Ext.create('Ext.window.MessageBox', { buttons: [ {text: "Ok", handler: function(){alert('hi');}}, {text: "Play", handler: function(){alert('hello');}}, {text: "that", handler: function(){alert('how are you');}}, {text: "funky music", handler: function(){alert('hola');}}, {text: "white boy", handler: function(){alert('coma esta?');}}, {text: "Cancel", handler: function(){dialog.close();}} ] }); dialog.show({ title: 'Save Changes?', width: 800, msg: 'Click OK to delete this item or click Cancel to exit', icon: Ext.MessageBox.WARNING });- Found potential solution
- change padding
- default css plus one addition($window-body-background-color: #ffffff !important; )
- WinXP
Removing padding-bottom from that via IE's dev tools appears to fix the issue. Normally I would just alter the scss for window. However, in this case the styling is being drawn on the element itself not via a class. My suspicion is that IE, being IE, is incorrectly handling padding and since the buttons are in a tool bar drawn with top/left it is choosing to draw them after the last physical thing in the mark up and over top of the padding.Code:<div class="x-container x-window-item x-container-default" id="container-1346" role="presentation" style="padding-bottom: 10px; padding-left: 10px; width: 590px; padding-right: 10px; overflow: hidden; padding-top: 10px;">
This looks fine in the newest versions of chrome and firefox. Also, removing the padding-bottom seems to have no change on the styling at least in chrome.
Thank you for reporting this bug. We will make it our priority to review this report.


Reply With Quote