I am using Firefox 18.0 here and Windowblinds with no issues at all. Now Thunderbird is another story, and you are right, the titlebars are all messed up. But as it does not occur in Thunderbird 16.0.1 and below, it is evidently something Mozilla did starting with Thunderbird 17.0 and up, and not a Windowblinds issue. But if Stardock could do something to compensate for and fix the issue however, that would be sweet!

I updated to 18 a couple of days ago without any issues at all. As for Thunderbird...don't use it.

I have fixed both problems by unistalling Windowblinds and re-downloading it direct  from the Stardock website (instead of downloading though Stardock Central).

I am running latest windowblinds and firefox18 with no problems.

removed the mess...[admin]

I believe you can fix mozilla. open what you see in the screen and enable menu bar.Will not fix thunderbird though.

Got me guys, supposed to be a screen capture!Wow.So, manual suggestions I guess.

Top left of your Mozilla screen, an orange tab, open with the arrow,hover to options, enable menu bar. Should get your buttons back. Will not work for thunderbird.You can still click on button area in thunderbird and close, just no buttons visible.

Stardock, sorry about the screen, guess I can not drag and drop images? Feel free to delete.

Thank you wizard, I wondered how that worked. Your always on top of things. Thanks again for the info.

Same problem here. Happens with all skins. Turning on the menu bar works, but it's a terrible workaround.

Need an update fast!

From LINK

[quote who="doortech1" reply="5" id="3308244"]removed the mess...[admin]

THANK YOU ADMIN> Apologies.

Just wanted to add, you could leave the menu bar off and still have caption buttons, but only when not in full screen. Some people do not browse in fullscreen, I usually do not. You can switch back and forth to fullscreen  by double clicking the top window frame area. Just more FYI.

That must've been some mess. Sorry I missed it. Double clicking on the top bar does the same as clicking on the middle button. what's it called again, min/max? 

Yes Uvah, but when there is no buttons I refer too. Obviously, buttons are more user friendly, but you need buttons first. Thanks wise guy.

I have a similar problem. But for me, when I use Windowblinds and Firefox 18, the FF screen starts up as normal then a split second later, the whole thing turns black. I have to move the mouse around a bit and click some stuff before I can get a usable screen again. When I try to disable FF from Windowblinds, I too am missing the buttons doortech1 speaks of. I've tried uninstalling and reinstalling and all that to no avail. I am currently using the default Win 7 skin and everything is working fine.

Black screen:

http://imageshack.us/photo/my-images/194/blackhl.jpg/

Missing buttons:

http://imageshack.us/photo/my-images/838/20130116060358.jpg/

Any suggestions? Am using the latest WB downloaded from the Stardock store. Oh, and I've tried doing showing/unshowing all the menu bars, bookmarks, etc. with no luck.

I've had problems with WB and Firefox since Firefox switched to the "unibar" layout a while back. If I try to use FF with the skin, it just keeps flickering and is completely unusable - my guess is WB is trying to skin a non-existent titlebar.

Never had any problems with WB and Thunderbird though.

Dunno if this'll help, but I solved my problem. Turns out I had to disable hardware acceleration inside Firefox. After I did that, everything reverted back to normal. Geez, if I'd only figured it out sooner...

Turning off hardware acceleration did it!  All of the control items display properly in menus and on web pages.  On top of that my font rendering is smoother.  I don't really notice much of a performance hit either.  Thanks Incognizant.  I was starting to blame many of the skins that I like for the problems until I realized that the problem was only when I was in FF.

Thank You !!

Finally, I am able to use FF properly.

disabling hardware acceleration did not fix it for me I'm on 19.02. Has any worked out how to fix this issue without enabling the title bar? Any feedback would be greatly appreciated, as this seems to have been going on for 3 months now, without any real resolution in sight.