199561 - [popup blocking] upgrading from ns7.02 with a blacklist

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[sairuh (rarely reading bugmail)]

spun off from bug 195928.

1. with ns7.02, create a profile which has "allow popups" and uses a blacklist.
(for simplicity, i cleared out the default whitelist as well.) here's what i had
in the blacklist:

netscape.com
resfest.com
hopey.mcom.com

2. quit and restart the profile using today's trunk (for me, commercial) build.

3. visit http://hopey.mcom.com/tests/unreqested-popup.html. results: the
notification icon appears in the status bar. however if i open the prefs panel,
"block unrequested popups" is deselected. (don't change the pref, though.)

4. visit http://resfest.com. a popup appears, and then i get the About Popups
dialog asking me whether i want to enable blocking.

5. click No in About Popups.

6. quit and restart profile in ns7.02.

7. view the blacklist.

results: upon returning to 7.02, the blacklist was cleared out. but why wasn't
it cleared before or at step 3?

[side note: if http://home.netscape.com was loaded at step 3 or 4, its popups
would *not* be blocked, or result in the About Popup dlg. since it'd be part of
the default whitelist, would this be expected anyhow?]

Comment 1

[Samir Gehani]

Nav triage team: nsbeta1-

Comment 2

[Robert Kaiser]

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

Comment 3

[Robert Kaiser]

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