Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

How do i turn off the fading effect of new status bar

  • 3 valiny
  • 3 manana an'ity olana ity
  • 5 views
  • Valiny farany nomen'i yawfle

vicpol
vicpol
more options

When you go over a link takes about 1 seconds to show the link in the new status bar.

I want all the effects removed from firefox so is as fast as possible. is there a way to do that? I have disabled all animation from about:config page but the status bar still takes forever to show up.

When you go over a link takes about 1 seconds to show the link in the new status bar. I want all the effects removed from firefox so is as fast as possible. is there a way to do that? I have disabled all animation from about:config page but the status bar still takes forever to show up.

All Replies (3)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

You can look at the pref browser.overlink-delay on the about:config page (default 70).

vicpol
vicpol Tompon'ny fanontaniana
more options

Thanks for your reply.

I set that value to '0' and the status bar still takes the same time to show up.

Any clues?

Cheers!

yawfle
yawfle
more options

At first, I also thought that setting that pref didn't work, but the next time I started the browser, the hover display was instantaneous, so apparently it required a restart for some reason.