-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install script notification toast notification fails to show up #1511
Comments
This is not an accident. Most users on Firefox 4+ have no status bar, so when the relevant code was re-written, this particular feature was not kept. I'll leave this open for now as a feature request to add it back, for if and when there's free time to work on it. |
Oh, thank you. |
Ah, you're referring to the toast notifications? Those should probably come back. |
Yeah, exactly, i am referring to the toast notifications, sorry for the unclear descriptions above. |
(Sorry for double-notification if my attempt there worked but ...) Can you check out the comment I just added at #1523 and respond? Thanks. |
Closing this as working as intended, based on feedback in #1523. |
Oh, thank you so much. Github did not give me a notification email. I just found the beta version will not automatically update so I made a update manually ,then i found the toast bar came back. It's 3 months later, thank you! |
Windows 7, Greasemonkey 0.9.15.
Firefox 10 and Firefox 4.0.1, new profile, only installed greasemonkey addon, both version have the same problem.
Before gm0.9.14, install a script will display "Fetching user script" and "installed successfully" message in the status bar. Since 0.9.14(include 0.9.15) this notification bar fails to show up, I tried a few scripts, all of them meet this trouble, no matter install from local or userscript.org.
After all, all the scripts installed successfully and works properly, the only problem is the notification fails to show up during the the installation process.
gm0.9.13 works properly, any one can help? Many thanks!
The text was updated successfully, but these errors were encountered: