Jason Bassford Reporter
	Description • 22 years ago

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021001
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021001

Carried over from bug 166442, this bug is to add a checkbox (perhaps as a
preference) to popup windows so that popup management is more easily exposed
than it is by context menus which have the following drawbacks:

1. They are "hidden" in that there is no obvious user indication that the
functionality is there unless somebody happens to right-click.

2. They can be made inaccessible if popup window is comprised of flash animation
or something else from which regular "page" context is not available to trigger
the appropriate context menu entry.

3. Context menus are disabled by the site.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

	Heikki Toivonen (remove -bugzilla when emailing directly)
	Comment 1 • 22 years ago

*** Bug 171966 has been marked as a duplicate of this bug. ***

	Dan M
	Comment 2 • 22 years ago

See bug 166442 comment 72 - 83 for a previous discussion containing reasons why
we should /not/ (and reasons why we should) add the popup blocking checkbox.
However there is an implementation waiting to go.

	Jason Bassford Reporter
	Comment 3 • 22 years ago

I don't know what the feelings are on making this a preference (I know, I
know...) but if it were, and it were disabled by default, I think that would
make everybody happy.  The current Popup Manager windows is new and, by
extension, so are all of its preferences so an additional "Show Disable Popup
Checkbox" preference would not be all that unreasonable.  I think.

	sairuh (rarely reading bugmail)
	Comment 4 • 22 years ago

->shliang

	Robert Kaiser
	Comment 5 • 16 years ago

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 6 • 16 years ago

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 7 • 16 years ago

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 8 • 15 years ago

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420