Open Bug 452894 Opened 13 years ago Updated 5 years ago

nsIAlertsService alerts sometimes get stuck in top left corner of the screen.


(Toolkit :: Notifications and Alerts, defect)

Windows XP
Not set





(Reporter: morac, Unassigned)



User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2008070208 Firefox/3.0.1
Build Identifier: 

I have a few extensions that can throw up nsIAlertsService windows at browser startup and occasionally when more than one alert is put up at the same time, one of the alerts will get permanently stuck in the top left corner of the screen instead of sliding up from the bottom right and then going away.

The only way to get rid of the alert at that point is to click on the window and press ALT-F4 on the keyboard to close the window.

I have no idea why it occurs and it isn't 100% reproducible, but the more alerts that pop-up at once at browser startup, the better the chances of it occurring.

Reproducible: Sometimes

Steps to Reproduce:
1. Display multiple nsIAlertsService alerts at the same time shortly after browser startup.

Actual Results:  
Every now at then one of them appears in the top left corner of the screen as a fixed window.

Expected Results:  
All alerts should display in bottom right corner.

I originally thought this was related to one extension displaying multiple nsIAlertsService alerts at once as this happened relatively frequently in one extension and others saw the same problem using that extension, but I just saw it occur when two different extensions both displayed a single nsIAlertsService alert right after the first browser window loaded.
I think i can verify the bug. I explained it here :

Summary : when the ubiquity code gets called for the first time, sometimes the popup gets stuck and i need to kill the firefox process to remove the popup.
Bulk move to Toolkit::Notifications and Alerts

Filter on notifications-and-alerts-component.
Component: XUL Widgets → Notifications and Alerts
Duplicate of this bug: 440449
You need to log in before you can comment on or make changes to this bug.