Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Previously selected links don't remain identified with a rectangle

  • 2 svar
  • 1 har dette problemet
  • 1 view
  • Siste svar av heynnema

more options

In previous versions of Firefox, I could view a web page with various links, and I could select a link to open in a new tab. Once I was finished in the new tab, I could close the new tab, and return to the original web page, and find the previously selected link because it still had a rectangle outline around it.

In the latest versions of Firefox, this rectangle no longer appears, so it's impossible to know where I was on the original web page.

Is there a way to get this feature back?

In previous versions of Firefox, I could view a web page with various links, and I could select a link to open in a new tab. Once I was finished in the new tab, I could close the new tab, and return to the original web page, and find the previously selected link because it still had a rectangle outline around it. In the latest versions of Firefox, this rectangle no longer appears, so it's impossible to know where I was on the original web page. Is there a way to get this feature back?

All Replies (2)

more options

Try the Firefox version from the official Mozilla server if you currently use a version from the repositories of your Linux distribution.


Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or userChrome.css is causing the problem.

  • switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Safe Mode start window
more options

How do I check "hardware acceleration or userChrome.css"?

I went to about:config, and I found both of them there. Changing "hardware acceleration" didn't have any effect. userChrome.css was an undefined boolean.

This problem cropped up in recent Firefox updates. I think it's a design change, or UI change. It's horrible. There must be some way to make it operate the way it did before.