Unable to click on extensions and swapping between windows is finicky

Description of the issue: When trying to click on any of these icons (mainly pinned extensions) the bowser flickers the menu of the extension without allowing further interaction.

Extensions

Additional issue is when windows (of Brave) are overlapped, trying to click into the window in the background, it runs into the same flickering issue. The window that was on the forefront stays and the one in the background flickers to the front and then immediately back. Both issues began roughly a week ago.

How can this issue be reproduced?

  1. Open 2 windows of Brave

  2. Overlap the 2 windows

  3. Attempt to click into the window behind the one currently on top

*The extensions issue is constant, just trying to click on them results in the menu flicker

Expected result: The window in the background is moved to the top, and the previously on top window is moved behind it.

Brave Version( check About Brave):

Brave 1.84.141 (Official Build) (64-bit)

Chromium: 142.0.7444.176

*Part of my own troubleshooting was updating to the latest version, I didn’t make note of the previous version (I was only a patch or 2 behind I believe).

Additional Information: The reason for placing both issues in this one request is due to the nature of the issue. In both instances, the “Customize and control Brave” menu is highlighted as if that was being clicked on instead. This can be seen in the included screenshot as well.

For the windows overlapped issue, I’ve found that I can get the window selection to change by clicking and dragging the one in the background. Any movement of the window forces the selection to update. Just making the window larger does not work (selecting an edge of the window in the background and extending it).

Found this post after creating this one, Unable to access the extension toolbar and search tab . Seems to have been a similar if not same issue with extensions. They were able to open the manage extensions menu from the toolbar. I’m unable to get that menu to appear but the rest of the behavior is the same.

After following the same troubleshooting steps the issue still persists. In Brave Nightly, both issues are not present. However, going back to the normal desktop version of the app, my issues still persisted.

@MXmilitia so you tried the new browser profile?

Also have to ask, are you using the same extension? (Bitwarden)

I did try a new profile, had the same issues. I even had issues creating the new profile because it makes a new window that has a pop-up that can’t be moved.

The extensions I’m using are not the same as the other post, just similar issue. The extensions I’m using are 1Password, AHA Music, and KellyC Show YouTube Dislikes. I tried disabling the extensions already as well, still the same issue for clicking in that area of the toolbar and the window selection.

You don’t by any chance have an AMD GPU, do you? I have run into some odd flickering/graphical corruption issues (not quite like yours, more like colored squares but holes in menus as well), and for me going to brave://flags and enabling “Skia Graphite” helped.

(It may or may not help, but if it does, I consider it more of a workaround than a “fix”.)

I have an Nvidia GPU (EVGA GeForce RTX 3070). I tried to enable the suggested item under flags and it had no effect (same behavior). After selecting “Disabled” to toggle it back off, I could no longer select/type in the search bar, however, I was able to open the extension menus without them flickering. This was as far as things went though as I was not able to interact with the menus for the extension even though they were visible now. I ended up resetting all flags to default again. After the reset, the menus reverted back to the glitched flicker.

Since it does seem switching to Graphite didn’t fix it, but altered the effect, it does point at least to the rendering pipeline as the likely culprit.

I normally don’t care about turning off hardware accelerated graphics in Brave, but this is one of those that at least will help pinpoint if it’s an internal Brave issue, or still in the rendering pipeline. So yea, try with hardware accelerated graphics disabled in settings, but this is just a test (it has the CPU do the rendering, not the GPU).

If that does work, perhaps see if there’s an Nvidia driver update? I’m doubtful as Nvidia drivers, while they had hitches earlier this year, usually don’t suffer these kinds of issues, but it might be worth checking just in case.

Accelerated graphics was already disabled, I vaguely remember doing this previously. I turned it on and it seemed to have no effect so I reverted back to having it off.

I checked for graphics driver updates a couple of days ago and applied the available update. This was part of my troubleshooting previously but the issue persisted. I checked for drivers again but Im already on the latest.

I don’t know what troubleshooting you’ve previously done unless you tell me. :wink: I don’t look through a users previous post, so all posts should re-iterate troubleshooting steps performed to prevent re-asking things.

At that point if graphics acceleration was already off, and your drivers are up to date, the issue likely is elsewhere, not on the rendering side. (Generally if graphics acceleration is off, and the issue persists, then the issue is nowhere on the GPU side oddly). I’ll need to leave this for another volunteer or a Brave developer to pick up. I’m out of ideas.

@MXmilitia would you be willing to download and run the Beta build of the browser and test to see if you get the same results there?

As suggested, I tried the Beta build. Browser worked entirely fine, no issues what so ever. I closed the Beta version and went back to normal Brave and everything is working again…

In the post that I linked earlier it said that the Beta and Nightly browsers were tested and then the issue was resolved. I misunderstood and thought it was just one version. It seems like something in the Beta version is fixing whatever bug is going on. Thank you!

Yeah that’s not a real solution though. I’m going to leave this thread open for now and if this issue occurs again please reply back here and let me know so we can dig deeper.

I agree that it shouldn’t be the answer but it was the only change between then, when it was not working, and now, when it finally was. I have since deleted both the Beta and Nightly versions to see if the issue returns but still no change.

1 Like