From the sounds of it you are using an older WB build as that's not a problem with Chrome that I am aware of.  You may need to uninstall, reboot and reinstall WB.

Regarding firefox, we have an update for that hopefully having QA testing next week.

Neil. Actually it is a problem with Chrome. I don't think it's a problem with WindowBlinds or SKS. What I have found out is all about how you position the buttons. If you position the buttons at the very top they work using Chrome. However they may be to high in the Explorer window. What I try to do is place them as high as I can in the Explorer window, especially when it is maxed. at least that way the buttons are visible in Chrome but the lower part of the button may be cut off a bit. The larger the buttons the more the problem becomes. I have gone to making a larger top frame and that helps.

So I would sum it up this way. Using Chrome the top part where the tabs are on is smaller in height then the Explorer top. Not sure you could actually do anything about that as it's the smaller height of the chrome window top versus the larger height of the Explorer top. 

Forget about what I said above. I changed to Chrome themes and it's fine. Tried five different ones and all good. Maybe I had some wrong theme on it. Who knows it's fine again.

If you go into the customize firefox settings and click the titlebar button to show the titlebar it fixes this issue

Someone get him an extra beer!

Thanks, mate.

Taking up browser real estate  by adding the title bar isn't a fix. It's a work around. This 'fix' was posted in the original thread reporting this issue with Fire Fox.

The issue is WindowBlinds for Windows 8.1, not Chrome.  Even with applying a custom Chrome, it doesn't always fix the issue.  If one continues to experience problems with Chrome or Firefox, they need to add chrome.exe and/or firefox.exe to the exclusion list within WindowBlinds settings.

Customizing the position of the titlebar buttons will cause issues in Windows 8.1.  It may show fine in explorer.exe, but there will exist issues within other window's titlebar buttons.  Thre reason for this is a poor WB integration with Windows 8.1's ability to adjust the font size for the Titlebar, which needs to be set at 14, otherwise clipping will occur. (The same poor integration causes some custom WB skin colors to revert back to stock Windows colors upon waking from sleep or hibernate, as well as causing font sizes to increase with each reapply of the WB skin. For example, setting all 5 custom font options to size 8 and the titlebar to 14, upon a reapply of the same skin, all the fonts set to 8 in CP - Display will increase in size with every subsequent WB skin apply.  This results in having to manually set the font sizes back to where they should be after every apply/reapply.)

On my PC Chrome is never skinned, no matter which nWB I use.  I don't have it excluded in the "per application" tab.    Should the WB frame and buttons be visible with Chrome?  I'm running the latest WB and Chrome versions on Win 7 64 bit.

Chrome frames should skin.  They will not skin if you have the DWM disabled as Chrome then paints its own look rather than let the OS do it.  Scrollbars etc do not skin in Chrome as they have their own look.

Regarding the Firefox update, I believe this was in QA on Tuesday so I am hopeful it will be passed by them and released soon.  It had other changes other than the Firefox tweak, so it took a little longer than ideal.

What's odd is if I get a chrome popup window it is skinned properly.  Otherwise it gets the standard chrome frame and buttons regardless of what blind I have installed.

Chrome 39.0.2171.71 m