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.

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

blue dot notification on pinned tab no longer consistently working

  • 3 replies
  • 2 have this problem
  • 1 view
  • Last reply by fm

more options

i use a pinned tab on a twitter account, and periodically go to it when i see the blue dot notification. not sure when it happened, probably with the latest horrible twitter display update, but i no longer see it. anyone know how its triggered, and how to bring it back?

thank you!

i use a pinned tab on a twitter account, and periodically go to it when i see the blue dot notification. not sure when it happened, probably with the latest horrible twitter display update, but i no longer see it. anyone know how its triggered, and how to bring it back? thank you!

All Replies (3)

more options

The blue dot is triggered by a change of the title, so if it isn't working then the page title may not be changing.

Just to be sure:

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 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

thank you ... tried turning on safe mode, went back to default theme, turned off hardware acceleration, same issue. i think you're on it on the title change. both sites i'm having issues with (one of which is twitter) show something like the attached image as an in page popup to refresh

more options

... and finally here is twitter doing it. does look like a change in page behaviour causing this.