URL displays in lower left of browser window while hovering over a link

Troubleshooting technical issues is much easier when both the user and support agent practice clear communication. For this reason, we have provided the template below for you to fill out with information about your issue. Please provide as much detail as possible so we can most efficiently resolve your problem.

Delete the any text above the line separator below before posting


Description of the issue:
How can this issue be reproduced?

  1. When I hover over a link on a web page, the url displays in the lower left of the window, about 1/4 of the way up from the bottom, covering up text in the window.

Expected result:

Brave Version( check About Brave):1.82.166

Additional Information:

1 Like

This is intended behavior and is common in most browsers. It is an important security feature to ensure that you can see that the URL for the link you are about to click on is pointing to where it claims to and not redirecting you to somewhere else [potentially malicious].

There is no way to disable this feature at this time.

This is NOT the intended behavior. The common/intended behavior is the preview shows at the absolute bottom of the window, not 1/4 of the way up as the OP is experiencing. I am having the same issue, Ubuntu Linux, offical Brave Flatpak build 1.82.166.

1 Like

1 Like

That is exactly what mine is doing also.

To be fair, Flatpak is never recommended and doesn’t work as well as the others. Like it says at https://brave.com/linux/

Brave is available as a Flatpak package from Flathub. While it is maintained by Brave Software, it is not yet working as well as our native packages. In addition, it modifies Chromium sandboxing in ways which have not been vetted by the Brave or Chromium security teams. We currently recommend that users who are able to use our official package repositories do so instead of using the Flatpak.

@WTerry8437 out of curiosity, are you using Flatpak as well?

@FrazerTurk @WTerry8437 also curious if you can advise if this works in a new browser profile and/or private window?

Additionally, if you change the setting for Use graphics acceleration when available which is at brave://settings/system, do you notice any change?

Or if you resize the window, does it start working differently?

Guess just trying to figure out a few little details.

Not sure…I got my Brave Browser at the Ubuntu App Store

To be fair, it has worked fine for over a year since I installed brave on that machine. The issue appeared about 2 weeks ago. Possibly after brave was updated?

Resizing the window does not solve or affect the issue.
Private window does not solve or affect the issue.
I do not use profiles in Brave, for privacy reasons (the reason I use Brave to begin with).
Unchecking “Use Graphics Acceleration” and relaunching does not solve or affect the issue.

Thanks for the ideas.

1 Like

How can you tell if it is Flat pack version?

If you installed from the Ubuntu Store you would 99% have installed a Snap version.

1 Like

Which I’m not positive, but when just doing a quick web search see some responses that this would be the SNAP version, of which Brave says a similar thing as it did with the Flatpak. I don’t have Linux so can’t test anything and not sure how simple it would be to grab from the other method:

sudo apt install curl

sudo curl -fsSLo /usr/share/keyrings/brave-browser-archive-keyring.gpg https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg

sudo curl -fsSLo /etc/apt/sources.list.d/brave-browser-release.sources https://brave-browser-apt-release.s3.brave.com/brave-browser.sources

sudo apt update

sudo apt install brave-browser

@FrazerTurk profiles in Brave aren’t anything online and wouldn’t really be anything negative to do with privacy. Browser profile is all localized on your device and just allows you to separate data. So like if you wanted one browser profile that is only for work and another for your personal, to which autofill and/or saved passwords would be there.

All browser profiles share the same changes to brave://flags and also any custom content filters in Shields. But most other settings and data in a new profile would be as if you just installed Brave for the first time while on that profile.

If you go to the hamburger menu (three lines) → More Tools → Add New Profile, then you can create a second one with whatever name you want. It’s a good troubleshooting step as it can kind of test if there might be settings or corruption in the normal profile. You can always delete the profile after if you want

That said, I’m doubting it would change anything. Just always good to kind of confirm.

Other thing I suppose @Mattches might ask if you all want to try is to get Brave Beta or Brave Nightly and see if the same thing happens there or is resolved.

I’ll try that and also install a second copy of Brave from the source you have quoted and report any changes.

1 Like

I tried resizing window…no change. I also tried changing the setting for “Use graphics acceleration when available”. Tried it both ways and closed browser after each change and reopened.

Installing from the repository had no affect on the issue. When I have more time I can try the Beta/Nightly builds and see if anything changes. I will say that generally, the “sandboxing” that is done by Flatpak shouldn’t cause issues with where something is rendered onscreen. I can see the sandboxing causing latency/connectivity issues or miscommunications with the desktop environment (like not having appropriate permissions to save files, for instance). Thanks for the help Saoiray.

1 Like

Nightly build installed from the repository has the same issue, both with acceleration on and off.

I tried Firefox and the URL line does appear when hovering over a link but it appears at the very bottom of the screen.

1 Like

@FrazerTurk thanks for checking. You wouldn’t happen to have Chrome installed where you could open and just verify if it’s happening there as well, would you? Basically confirmation whether it’s specific to Brave or if it might be Chromium based?

Outside of that just would be trying to think if it’s scaling as an issue. I was reading where people made adjustments to DPI and all when they had issues in the past.

While doing some research just now, saw one suggestion of --force-device-scale-factor=1.25 or --force-device-scale-factor=1 just to test if scaling impacts it.

But at this point would be nice just to see if Mattches can try to get someone check Ubuntu to see if they can replicate it. I forget if he has direct access to Linux or if he’d have to loop someone in from Brave to test. But either way, at least have the two of you seeming to be having the same problem. So good to check into.

Which can be useful as a basic check, but Gecko versus Chromium/Blink is more like comparing apples to oranges. The better test would be to verify whether two Chromium-based browsers, especially Chrome itself, show the same behavior.