White border appearing around drop down menus on Linux

[Brave-Matt]

White border appearing around drop down menus on Linux

[harridu]

Actually I don't think I need a compositor, losing control over the background of my desktop and introducing other weird side effects. What I do need is some checkbox in Brave to turn off a graphical gimmick I didn't ask for.

Please don't make the eye-candy mandatory. There is no such problem for Google Chrome, for example. Thank you

[pythys]

I also confirm this bug. Arch linux on i3wm

[suryaanshah]

can confirm the same on v1.67.116 LinuxMint

[dmitrykvasnikov]

The same on Arch / i3 (GTK themed) with v1.67.116

[Utsunom1ya]

Garuda/Archlinux with Hyprland.
6.9.4-zen1-1-zen kernel.

[GoWeasel]

I also confirm this bug. Arch linux on i3wm

• same on Manjaro XFCE
• • brave-browser 1.67.116-1 [Installed])
• • 6.9.3-3 Kernel

[rmdhnreza]

Chrome issue 40937108

TL;DR: On X11, you need a compositor to draw shadows. xcompmgr should be enough.

[pythys]

@harridu I think the problem actually originates in Chromium and not necessarily in Brave. It seems to be just more visible in Brave. When I open the menu in dark mode in Chromium I still see some "weird" white that is just more tiny. Take a look below, do you see the white corners? That's possibly the same shadow bug.

[inicula]

Why wasn't this a problem before 1.67? Did this type of menu not have shadows or what?

[harridu]

You are right, I didn't notice the white corners. It is not as distracting as Brave's giant white frame. Maybe Brave could reduce the white frame?

I would prefer to skip all that eye-candy, but I understand that this would be an enhancement request to chromium.

[pythys]

@harridu Fixing the border might be fixing a mistake with another mistake. The root cause is shadow rendering and I would imagine that's what the brave team should attend to.

If you are annoyed from this bug (as I am) then downgrading is a simple quick solution. I downgraded to version 125.1.66.120 and as the screenshot below shows things are pretty peachy at the moment.

[Cthulu201]

I agree we shouldn't be required to have a compositor, but xcompmgr looks better than picom on my Arch/i3 setup. FWIW in the interim.

[egbastos666]

I completely disagree that composite usage should be mandatory. That's a complete useless "eye-candy" feature that brings nothing to the end user rather than something "beautiful". There are a lot of linux users that really doesn't care about this kind of things, that uses i3wm, that uses fluxbox exactly because they are simple and use minimal resources and we don't want to run an additional component just to "looks pretty". I think that the best way to handle that is to include a flag on chromium that makes possible to disable composite usage run without any shadow or this kind of things