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

Notification "symbol" doesn't go away in pinned tabs after I open them (Version 47 of Developer Edition)

  • 2 replies
  • 1 has this problem
  • 2 views
  • Last reply by ERap320

more options

As the title says I have a problem whith my pinned tabs. Let's take facebook as an example. When I get a message from someone, the blue dot which indicates a notification appears under the favicon. The problem is that it doesn't go away even after I check everythig that could generate the notification. I don't think it is caused by specific websites since I have different tabs that i leave always pinned, and this behaviour showed up in all of them after the update to version ~47 (I can't remember the specific one).

As the title says I have a problem whith my pinned tabs. Let's take facebook as an example. When I get a message from someone, the blue dot which indicates a notification appears under the favicon. The problem is that it doesn't go away even after I check everythig that could generate the notification. I don't think it is caused by specific websites since I have different tabs that i leave always pinned, and this behaviour showed up in all of them after the update to version ~47 (I can't remember the specific one).
Attached screenshots

Modified by ERap320

Chosen solution

Thank you! I tried to disable one add-on at a time and I found out NoScript was the culprit.

Read this answer in context 👍 0

All Replies (2)

more options

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

  • Switch to the DEFAULT theme: "3-bar" menu button/Tools > Add-ons > Appearance
  • Do NOT click the "Refresh Firefox" button on the Safe Mode start window
more options

Chosen Solution

Thank you! I tried to disable one add-on at a time and I found out NoScript was the culprit.