Bei mir tritt das gleiche Problem mit Firefox auf. Scheinbar haben die Programmierer gar nix gefixt sondern einfach die 8.1 nach langer Zeit einfach so rausgehaun. Firefox crasht gleich nach dem ich Firefox gestartet hab.

Translation: Same problem occurs here with FF. Seems like the programmers did not fix anything at all, just thrown out 8.1 after a while.

FF does crash right after i start it 

benmanns: I wonder what happend to my reported chrome issue...is chrome to powerfull?
I just dont understand why you cant find a solution to the problem or get in contact with the developers to solve the pixel gap issue.
If i use WB im kinda forced to one of those lesser browsers to have a decent experience on my OS 

Which addins do you have in firefox, do you have any tools running which alter Direct3D settings in games and is this normal firefox NOT firefox developer edition?

The pixel gap issue IS fixed with Chrome as long as you have a modern graphics card (DX11 capable).  If your card is DX9 it will remain.

If it is still there then please uninstall WB, Reboot (Critical), and reinstall WB as it may be some files have not been replaced.

I have checked here and Waterfox 36.0.1 is working just fine on a Windows 8 test box.  Firefox developer edition is not, but as I have said I think that's being upset by the normal firefox fixes.

why does mine say 8.09

If yours says that then it has not been updated properly.

Can you uninstall, reboot and then reinstall.

How did you install originally?  From standalone installer, or via ObjectDesktopManager?

Brad had me run a purge tool, reboot, and reinstall WindowBlinds. I chose one of the default skins and rebooted again for good measure; didn't change any other settings. It didn't change the results—Firefox Developer Edition and Waterfox both still crash immediately.

I ran the SD Support Tool and sent the results to Brad in the hope that it will assist in reproducing the issue.

I can make do with standard Firefox for now, since I figured out how to run two instances simultaneously (with the -no-remote command line parameter); one with my Waterfox profile and one with my Developer Edition profile. Still would really like to see this fixed soon.

awesome will try that

We have an update in internal testing which should address firefox developer edition crashing and other derivatives based on the beta firefox 37.

I believe this will be slipstreamed vs having a different version, but I will post here when it is ready.

Neil, as usual, you are awesome. Thanks for all you do.

I've updated twice now from the stardock store and mine still says version 8.06

Have you tried running a register clean up after uninstall before reinstalling 

Just FTR, Neil's professionalism is second to none.  He's a gentleman in the truest sense of the word.  Fourteen years I've been observing here, he's never once been anything but.

I have just checked here and see no issues with Opera 28 and WB 8.1.  The titlebars seem to be skinning just fine.  Could you contact [email protected] so they can collect some more information please.

@ 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.