Issues with Google Chrome

from Stardock Forums

Well, it should come as no surprise that I am having issues with using Google Chrome with WindowBlinds 7.

They do not get along, but I can live with that. 

My problem is that creating an exception for Chrome does not work. Chrome just goes along happily using the same skin as the others.

Another issue that I am having is that when I maximize a window of any kind, the title bar likes to hide behind the taskbar (I am using a Mac OS skin, so I like having the taskbar on top).

I never post in forums, hoping that I will find that someone else has had the same problem, but the solution provided to those people (creating an exclusion) doesn't work for me at all. I don't want to choose between WindowBlinds and Chrome. Chrome will win, but I'll be sad.

Please help me.

windowblinds
7,195 views 17 replies
Reply #1 from WinCustomize Forums Top

If you could post some screenshots of what you are seeing that would be very helpful.

Choosing between WindowBlinds and Chrome is like apples and oranges, they do different things.  I would keep WindowBlinds. 

Question, do you keep your browser window open all the time or just when you are browsing?  In other words if it is only open when you are using it......... :-"

Using the exception to not skin Chrome with WBs should work, you just have to tind the .exe

SoundPackager - Customize the Windows sound scheme
Reply #3 from WinCustomize Forums Top

Chrome has never played well with WB for me, whether it's titlebar buttons not working properly or controls not being skinned.

Reply #4 from Stardock Forums Top

Quoting Neil, reply 2
Which OS are you using?
End of Neil's quote

^This...^

And make sure you're pointing to the right file.  Google puts it in an odd place...

XP: C:\Documents and Settings\YOURUSERNAMEHERE\Local Settings\Application Data\Google\Chrome\Application\chrome.exe
Vista: C:\Users\YOURUSERNAMEHERE\AppData\Local\Google\Chrome\Application
7: C:\Users\YOURUSERNAMEHERE\AppData\Local\Google\Chrome\Application

Reply #5 from WinCustomize Forums Top

Yep, Google Chrome is not skinned properly and adding an exception doesn't help (Vista HP 32 bit and Chrome 4 Beta Portable). I added 2 exceptions for Chrome.exe and ChromeLoader.exe (probably not necessary).

Reply #6 from WinCustomize Forums Top

It is very important that screenshots are provided.

Reply #8 from WinCustomize Forums Top

No, I need a screenshot of the problem with it when skinned, not when excluded.

Reply #9 from Stardock Forums Top

Shouldn't it be obvious what is messed up when skinned if he said that adding an exception has no effect?

 

Anyway, looked like that to me too (when skinned) and adding an exception has no effect.  I would imagine just loading up google chrome will give you the problem too.

Reply #10 from WinCustomize Forums Top

Quoting ShawnClapper, reply 9
Shouldn't it be obvious what is messed up when skinned if he said that adding an exception has no effect?

 

Anyway, looked like that to me too (when skinned) and adding an exception has no effect.  I would imagine just loading up google chrome will give you the problem too.
End of ShawnClapper's quote

 

some people just aren't very bright.

 

Reply #11 from Stardock Forums Top

By the way, messing around with it and it seems if you have a google chrome theme installed it doesn't reskin the border so not everyone will see all the problem.  It does however still change the scrollbar from Vista Aero to crappy grey windows 2k look.

Reply #12 from WinCustomize Forums Top

The controls changing to classic in Google Chrome is normal.  The sandboxing used by Chrome originally supported WB, but changes to it have since prevented WB from skinning them.

Reply #14 from WinCustomize Forums Top

Excluded the controls would still be classic and the frames would also be forced at best into the ugly blue they are when on XP.

If you want to stop the frames skinning, applying any Google Chrome skin should override WB.

Regarding Iron.exe mentioned earlier, this is not detected as Google Chrome which is why there were problems with that one.  This should be sorted with WB 7.01 that was released today.

Reply #15 from Stardock Forums Top

Also noticing that pop up windows have no controls on them.  Cannot close them except for right clicking taskbar and choosing close window.

Reply #16 from WinCustomize Forums Top

What the heck, man. How can you not be able to at least *exclude* an application?? I'm not a programmer, but I love Chrome, and the "Classic" grey scrollbar Chrome uses any time I use a skin is driving me batty -- and away from WB. Aren't there enough people using Chrome to force you guys at Stardock to fix this?

Reply #17 from Stardock Forums Top

What makes you assume that the problem is something that can be fixed in WB, vs something that Chrome is doing which can't be overridden?