Split Monitor Padding + Chrome

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

If you are experiencing any issues with your desktop wallpaper or taskbar buttons
please download and install the latest DisplayFusion beta version before contacting support.

<< Discussions Reply

A_Li_N

2 discussion posts

I have a 4k setup and I have split my screen into 6 sections.

Chrome appears to be acting very oddly when maximized inside the splits. The first window opened gets a black border around it, about 20 pixels wided. This causes the actual Chrome window to appear to have a 20-pixel black padding.
Any subsequent Chrome windows do not have the black border, but retain what looks like a 20-pixel clear padding.
It's almost as if DF is adding in the default window border of a normal Windows window.

See the attachment for a screen capture; the highlighted area at the top shows a corner of the 'first' window (top-right) and subsequent windows (bottom-right and top-left). The highlighted area at the bottom shows a Writer window, which has no padding around it (other windows with standard bars show just fine as well).

All paddings are set to 0. Can anyone else confirm that Chrome gets a border/padding around it when they use Split Monitor?

• Attachment: Capture.PNG [32,488 bytes]

Capture.PNG

Jan 29, 2015 • #1

This is more of an issue with Chrome, in that it doesn't render its borders correctly when maximized. This only happens with Chrome using a custom theme, or if your Windows theme set to Aero Basic or Classic. We've come up with a possible solution/workaround for it though, so I'll be sure to let you know when we're able to implement it so that you can test it out.

In the meantime, as a workaround, you can set your Windows theme to Windows 7 Aero, and make sure that you're using the default Chrome theme :)

Thanks!

Jan 30, 2015 • #2

A_Li_N

2 discussion posts

Resetting to default theme works and I'll use that for the time being. Thanks for letting me know and for sure let me know when the update is in place!

That, or I'll just check the change logs as updates come in

Feb 3, 2015 • #3

We've just released a new DisplayFusion beta version (http://www.displayfusion.com/Download/Beta/) and this issue should be all fixed up. Please let us know if you run into any trouble after updating.

Thanks!

Mar 12, 2015 • #4

Olivia Cres

1 discussion post

The beta did not resolve this issue for me.

Windows: 8.1
Chrome: Version 44.0.2391.0 dev-m (64-bit)
Resolution: 3840x2160

Code
Copy
Select All

Name: DisplayFusion Pro 7.2 (Beta 5)
Name Data: DisplayFusion
Build Date: Apr 24, 2015 21:45
Operating System: Microsoft Windows NT 6.3.9600.0 (6.3.9600.0)
Operating System Name: Microsoft Windows 8.1 Pro
Is Server: False
Is Windows 8.1 Update 1: True
Detected Version: Win81 / Svr2012R2 (Win81 / Svr2012R2)
x64 Process / System: True / True
Date/Time (UTC): 05/08/2015 00:54:40
Date/Time (Local): 05/07/2015 19:54:40
.NET Framework: 2.0.50727.8009

Still have the borders and spacing exactly as shown in the screenshot. This may be due to me using the dev version of chrome? But I doubt that. It doesn't bother me too much so I leave it as is. However, changing back to the default layout does resolve the problem.

I use Chrome with two different user accounts and the skin is how I distinguish the different windows (work and personal)

Mostly just wanted to let you know it's still an issue.

May 8, 2015 (modified May 8, 2015) • #5

Ok, thanks! We had tried something to resolve this issue, but had to roll back the change as it didn't work out too well. I have another workaround for you though. You can setup a Custom Function that will size the window to be 100% of the split, instead of trying to do a real maximize. Please see the attached screenshot for reference.

After setting up that function, you can select it in the list and click "Toggle TitleBar Button" so that you can access it easily in the titlebar of Chrome :)

Hope that helps!

• Attachment: SizeTo100Percent.png [69,898 bytes]