1880817 - Notification dot of pinned tab stays even when notifications have been cleared

Status: RESOLVED INCOMPLETE

(Firefox :: Tabbed Browser, defect)

Description

[linkcharger]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0

Steps to reproduce:

1. Open a website that sends notifications (eg. Gmail)
2. Pin it
3. Wait for notification to occur (eg from new email) -> the pinned tab has a little dot
4. Clear notification (eg. go to Gmail tab, read new email)
5. Go back to other tabs

Actual results:

6. Notice that the notification dot is still there

To clear the dot, go to the pinned tab once again (now without a notification from the website), go back to another tab -> now the dot is cleared.

Expected results:

Once I visit a tab of a website that sent a notification signal and clear the notification, it should no longer display the dot in the tab.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Negritas Sergiu, Desktop QA]

Hello! I have tried to reproduce the issue with firefox 125.0a1(2024-02-20) on Ubuntu 22.04 and Windows 10, unfortunately I wasn't able to reproduce the issue on my end.
Could you please answer the following questions in order to further investigate this issue:

1. Does this issue happen with a new profile? Here is a link on how to create one: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
2. Does this issue happen in the latest nightly? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
3. Do you have any addons installed? If yes could you please list them?

Comment 3

[linkcharger]

(In reply to Negritas Sergiu, Desktop QA from comment #2)

Hello! I have tried to reproduce the issue with firefox 125.0a1(2024-02-20) on Ubuntu 22.04 and Windows 10, unfortunately I wasn't able to reproduce the issue on my end.
Could you please answer the following questions in order to further investigate this issue:

1. Does this issue happen with a new profile? Here is a link on how to create one: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
2. Does this issue happen in the latest nightly? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
3. Do you have any addons installed? If yes could you please list them?

Hi! Thanks for your attempts.

1. It does not happen in a new profile (
2. It does happen in a fresh nightly install (new profile and no addons)
3. Yes, I have addons:
   Dark Reader
   Download All Images
   Ecosia - The search engine that plants trees
   Everything Metric - Auto Unit Converter
   Firefox Relay
   Firefox Translations
   I still don't care about cookies
   Return YouTube Dislike
   SponsorBlock for YouTube - Skip Sponsorships
   Take Webpage Screenshots Entirely - FireShot
   uBlock Origin
   Video DownloadHelper
   Wikiwand: Wikipedia Modernized

As I was testing this I observed some more details:

1. I receive an email
2. The dot appears
3. I switch to the tab
4. The dot disappears even when I have not marked the new email as read - I suppose the dot just represents unread notifications in this tab in general, not any particular items on the page.
5. I go to another tab
   6. There is a delay of about 10-20 seconds
6. The dot re-appears (without any new notification event to trigger it)

Further, the behaviour (both the dot appearing originally and later re-appearing) does not seem to be consistent - sometimes the dot appears, sometimes it does not. So in the above reproduction, it may still happen with a new profile - maybe it just did not randomly appear in the few times I or you have tried to reproduce it. Is there a way to reliably trigger either a notification from a website, or even better, the 'unread notification' event in Firefox? That would allow us to rule out that these inconsistencies come from Gmail or other sources, for instance.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:mak, could you have a look please?

For more information, please visit BugBot documentation.

Comment 5

[Marco Bonardo [:mak]]

(In reply to linkcharger from comment #3)

3. Yes, I have addons:

because add-ons can interact with pages, they may also be the cause of the bug here.

4. The dot disappears even when I have not marked the new email as read - I suppose the dot just represents unread notifications in this tab in general, not any particular items on the page.

It's supposed to go away as soon as you interact with the tab.

5. I go to another tab
   6. There is a delay of about 10-20 seconds
6. The dot re-appears (without any new notification event to trigger it)

AFAIK, the dot appears when a pinned tab receives a "titlechanged" notification, so the site changed or set its title, that is normally an indication contents changed or something new arrived.
I cannot reproduce the bug with gmail, do you have other example of sites where this happens consistently?

Further, the behaviour (both the dot appearing originally and later re-appearing) does not seem to be consistent - sometimes the dot appears, sometimes it does not. So in the above reproduction, it may still happen with a new profile - maybe it just did not randomly appear in the few times I or you have tried to reproduce it. Is there a way to reliably trigger either a notification from a website

I suppose you could write a test page that changes the title every N minutes, though I'm not sure it would be useful to debug the intermittent behavior you're seeing, that may be specific to an add-on or pages.
It would be better to try using the browser without add-ons for a while (like a couple days) and see if the behavior persists.

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Given that the bug is still UNCONFIRMED, closing the bug as incomplete.

For more information, please visit BugBot documentation.