@ knuddibeier gerade wird ein update intern getestet das eventuelle Fehler mit der FF developer Version behebt, ruhig Blut bis dahin
Ps: Ein schönes Wochenende 

Oh are you seeing this when applying a WB skin with opera open?

If you have switched from the OS skin to a WB skin you will need to close all instances of Opera and open new ones.  This is due to their sandboxing system.  This also applies to Google Chrome.  Switching from a WB skin to another WB skin does not require that.

Well I also am a longtime window blinds and Stardock user and a really upset about the issue in not seeing the bar in Firefox, on top. I am using windowblinds 8.1 and problem is still not fixed. It's beginning to seem like a waste of money to me also.

There are clearly machine/driver differences to be accounted for, since two of my Win7 Pro rigs run Pale Moon without any WB 8.1 issues and one rig has a recurring transparent titlebar in PM.  It gets skinned correctly by re-applying WB from the config dialog.  Is that the case for you, terry696?

@benmanns danke für die Info hab sowieso momentan nur aero style von win7 an in der Zeit.

Just to keep this thread up to date....

Brad asked me to try turning off hardware acceleration. This prevented the immediate crash in both Firefox Developer and Waterfox, but the titlebar issue remains. And I don't want to run without hardware acceleration.

Further to the above....

The titlebar issue reappears in standard 32-bit Firefox when hardware acceleration is turned off.

can we make it so i can do this on windows 10 not going back to 8 just to run a update

Firefox auto-updated to version 37.0 today. Now it also crashes on launch with WindowBlinds loaded. Hardware acceleration setting makes no difference. I have no choice but to stop using WindowBlinds now.

It's just such an excellent product, it's hard to live without. Windows 8.1's default styling is terrible.

At least I can get shadows with ShadowFX.

The understatement of 2014.

2 nd that

We have the v8.11 update out that addresses the Firefox issue. Please try that update and let us know if it resolves your issue.

https://forums.stardock.com/463084/page/1/

Beautiful! Waterfox, Firefox Dev, and standard Firefox 37.0 are all working. Great job, guys!

Oops ... almost perfect. There seems to be just a very minor issue:

In Firefox dev and Firefox 37.0 (but not Waterfox), the titlebar sometimes loses transparency. It seems to happen when switching to Firefox from another application, sometimes when moving the window, and sometimes when the mouse has been over the titlebar and then moves away. The titlebar doesn't go completely opaque, but becomes about half as transparent as it should be. When it happens, there's often a hard black shadow behind the top of the window, except for where the window controls are.

Here's a screenshot showing the issue with the Acrylic skin.

At least it's usable! Still looks much better than raw Windows 8.1.

You would need to speak to the firefox devs about that one.  Notice how it is rounded around where the OS buttons would be...

Seriously? Why would it be the Firefox devs' responsibility to make it work with WindowBlinds? How could I possibly convince them to do anything about it?

Sorry I originally thought you were talking about the black bar which appears on maximized Firefox developer edition windows with a small rounded rectangle for the min, max and close buttons.  This is something only the firefox developers can change.

There does seem to be an issue with some transparent themes which is linked to repainting areas and we have a small tweak for the release version of WB 8.11.

Ah, okay. Glad we're on the same page.

As to hardware/driver differences, there is a tab background image in Pale Moon which displays on two of my rigs and not on the third; interestingly, it does not display on the rig which has the intermittent transparent titlebar on launch.  I prefer the background to not display, so that's good on the one rig, but ugly on the other two.  All three have the same versions of OS & WB.  I mention this again because I believe we should be mindful of machine differences and not expect WB to perfectly account for all of them.  Not saying that's the case for any poster's specific issue.  Just a general comment.