Incluse a feature that lists messages that the user told not appear again.




14 years ago
13 years ago


(Reporter: kevinar18, Assigned: bugzilla)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050307 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050307 Firefox/1.0+

There are several features in Firefox that display pop-up alerts (or some other
form of an alert) to notify the user of something that occurred.  Several of
these notifications include an option to have the alert never appear again. 
While this is very useful, on thing that is lacking is an easy way to re-enable
these messages again if the user accidentally dismisses them or wants them back

Two examples of these messages include:
The warning that appears when you try to close a window with multiple tabs open.
The yellow bar that appears when a pop-up is blocked.

A solution would involve having some kind of feature either included in the
options window, or via a link on the Tools menu that would show all of these
dismissed windows, notices, warnings, etc... and allow the user to re-enable
them, if they so desire.

In addition, perhaps a message could be included on some of these pop-ups to
notify the user of how they can re-enable the notices if they accidentally close
them.  Then again, I'm not sure if this would clutter the UI or not.

Reproducible: Always

Steps to Reproduce:
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.