[xmonad] Transparent Border with Chrome Beta/Unstable

[Zev Weiss]

I can't say with certainty if Chrome's unsightly-transparent-border problem is due to this, but at least for evince (which I've actually since stopped using in favor of zathura, for what it's worth) I was able to work around the problem by putting the following in ~/.config/gtk-3.0/gtk.css:

.window-frame, .window-frame:backdrop {
	box-shadow: 0 0 0 black;
	border-style: none;
	margin: 0;
	border-radius: 0;
}

.titlebar {
	border-radius: 0;
}

(Can't claim credit for that myself, found it via a google search some months ago and no longer remember where or what the relevant search terms were.)  Maybe hackishly useful in lieu of a "real" fix though?


Zev

On Dec 6, 2014, at 4:41 PM, Eyal Erez <oneself at gmail.com> wrote:

> Chrome has finally upgraded and now the stable version is exhibiting the same behavior.  I've also noticed that evince (document reader) is also showing a really ugly transparent gap around the edge.  I've attached a screenshot to illustrate the problem.  The two chrome windows and evince have the faulty transparent gap.  However, other windows are not (e.g. emacs and rxvt on the right).
> 
> Does anyone know how to fix this?
> 
> On Tue, Oct 21, 2014 at 2:57 PM, Brandon Allbery <allbery.b at gmail.com> wrote:
> On Tue, Oct 21, 2014 at 2:27 PM, Eyal Erez <oneself at gmail.com> wrote:
> I've recently update my machine to find that chrome's window border (orange on all my other windows) is now transparent.  I noticed that Google have added their new Aura graphics stack instead of GTK+, and I'm wondering if this is not playing nicely with xmonad.  Downgrading to Chrome stable solves the problem.  But I'm guessing that once the stable version gets updated, I'll get the same issue again.
> 
> Is anyone else seeing this?  Is there anything I can do to confirm that this is the problem or fix it somehow?
> 
> One drawback of using server side borders is that the transparency behavior is defined by the application, since the border is technically part of the application window and not a frame window. It may be possible to specify the border color as RGBA (e.g. focusedBorderColor = "#ffa500ff") instead of RGB... but this may then break (i.e. cause BadMatch X11 errors) windows which are *not* RGBA.
> 
> (The #xxx format for colors may not work for RGBA; it may need to be "rgba:1/0.65/0/1".)
> 
> -- 
> brandon s allbery kf8nh                               sine nomine associates
> allbery.b at gmail.com                                  ballbery at sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
> 
> 
> 
> -- 
> Eyal Erez <oneself at gmail.com>
> 
> There are 10 types of people, those who know binary and those who don't.
> 
> <2014-12-06-173823_3440x1440_scrot.png>_______________________________________________
> xmonad mailing list
> xmonad at haskell.org
> http://www.haskell.org/mailman/listinfo/xmonad