notification popups appear blank for a second



Mail Window Front End
a year ago
4 months ago


(Reporter: Ray Satiro, Unassigned)


(Blocks: 1 bug)


Firefox Tracking Flags

(Not tracked)



(1 attachment)



a year ago
Created attachment 8818605 [details]
blank notification.PNG

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce:

I have notification popups enabled so that when there is new mail there is a popup with the subject.

Actual results:

Sometimes I hear the notification sound and there is a popup but it is blank for a few seconds before showing me the subject of the e-mails.

Expected results:

It should not make the sound or show the popup until the text is ready to be displayed. I'd guess this has something to do with my mail provider since their server sometimes lags.
perhaps related to one of these
Component: Untriaged → Mail Window Front End

Comment 2

a year ago
Thanks, I've reviewed those but none of them are similar. After reading bug #1100973 it may be relevant that I have mailnews.customDBHeaders set to ' Received'. Also as I mentioned the notifications appear blank for just a second or two but eventually show up, it seems to be arbitrary. My guess would be something to do with yahoo's mail server, it's slow sometimes. Like today when I try to open a message it takes a few seconds.

Comment 3

a year ago
I've seen this in a slow debug build. I don't think this is a big issue. Who says that computers always work without noticeable delay? ;-)
Severity: normal → minor
Are the messages involved being filtered to non-Inbox folders?
Blocks: 36011
Flags: needinfo?(raysatiro)
See Also: → bug 1100973

Comment 5

a year ago
(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #4)
> Are the messages involved being filtered to non-Inbox folders?

Flags: needinfo?(raysatiro)

Comment 6

10 months ago
I've been seeing this fairly consistently - several seconds, not just one sec.
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.