default css plus one addition($window-body-background-color: #ffffff !important; )
By default, window body inherits the background color from it's parent which is a blueish hue. My company wants to add custom styling so that it looks similar to the above image. As such, we created a custom theme which at the moment only has one change which is adding the background color of white to window-body-background.Doing this causes the buttons to get overlapped by the white background. Some investigation has lead me to this portion of the markup
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.
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.
Short answer, yes it appears to work fine in 4.1 beta 3. However, it appears there are some other bugs with custom themes in the beta. If I run the themes example with resources/css/ext-all.css it works fine. However, switching to a custom theme(no changes just different file) cause some weird spacing issues. Also, the tabs styling appears to have additional issues(see below). This behavior seems fairly consistent among other examples I've tried as well.
I've not tried to debug the below behavior at all as it's really a separate issue. I'm not sure how soon 4.1 will be out of beta status either. Perhaps these are known issues. I've not looked. But, I'm not sure we can upgrade to the beta with issues such as this and I'm not sure my QA will let my code through with the issues I have in 4.0.7. untitled1.jpguntitled2.jpg
I noticed today when messing around with this that a page built with ext-all.js and only a message box appears to work correctly in 4.0.7. The example page for theme is using bootstrap instead of ext-all.js and displays as I screen capped above.
In 4.1 beta 3 they have converted that theme example to ext-all.js. I'm thinking the issue has something to do with bootstrap and if I avoid that I think things may be ok.