Open Bug 652051 Opened 13 years ago Updated 1 year ago

favicon does not changing at gmail when new mail arrives

Categories

(Firefox :: General, defect)

4.0 Branch
x86
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: antigluk, Unassigned)

References

()

Details

(Whiteboard: [platform-rel-Google] [platform-rel-Gmail])

User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20110321 Firefox/4.0
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20110321 Firefox/4.0

when new mail arrives in opened tab with gmail, favicon does not change.

Reproducible: Always

Steps to Reproduce:
1. open gmail.com
2. wait until the message comes

Actual Results:  
favicon is old!

Expected Results:  
favicon must contain the number of unread messages
Could you please confirm if javascript is disabled/enabled

With javascript disabled favicon do not display the # of unread messages
Yes, of course, js is enabled.
When i open gmail, count of new messages is on favicon. But it does not changes, even if i mark all messages as read.
I suppose the feature discussed here is the non-standard Google Labs extension "Unread message icon". Google calls that "Some crazy experimental stuff" and "They may change, break or disappear at any time". Anyway...

Works unreliably for me with:
Mozilla/5.0 (X11; Linux x86_64; rv:6.0a1) Gecko/20110419 Firefox/6.0a1

One thing that I dream up is that it works more reliable when running Gmail in a non-pinned tab than in an app-tab. Someone else who has done the same observation?
I've also found that there is some kind of interference with the Gmail Priority Inbox. The favicon gets updated when a mail magically jumps from "Everything else" to "Important and unread".
Google Labs extension "Unread message icon" sometimes shows the mail count for priority messages and sometimes for all the  unread messages.
Version: unspecified → 4.0 Branch
Whiteboard: [platform-rel-Google] [platform-rel-Gmail]
platform-rel: --- → ?
platform-rel: ? → ---
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.