182998 - Pop-up window page is also loaded in parent window

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Max Alekseyev]

This bug is discovered as a side effect of bug 170454
Testcase html is coming.

To reproduce:
1. Open testcase html
2. Click on link "How does Proxy bidding work?"
3. It will be opened in a pop-up window and at the same loaded in the parent window

Expected result:
Link should be loaded in pop-up window only.

I see the bug on OS/2 and Linux builds 2002120121

Comment 1

[Max Alekseyev]

Attachment: Testcase html

Comment 2

[Matthias Versen [:Matti]]

Reporter:
wfm with a 1 day old win2k cvs trunk.
Do you block popup windows ?

Comment 3

[Chris Lyon]

WFM 20021130 on WinXP

Comment 4

[Max Alekseyev]

Yeah, scripts are disallowed to Open unrequested windows here.
But I've just tried to allow that. It didn't help much. I still see the bug.

Comment 5

[Matthias Versen [:Matti]]

Please try a new profile. (it's possible that you have an old popup blocking
pref in prefs.js)

Comment 6

[Max Alekseyev]

Matti, probably you're right. I don't see the problem with OS/2 build 2002120112
on another computer.
But I don't like idea to recreate a profile. I would like rather to find out
that old popup blocking pref in prefs.js, and remove it. How to do that?

Comment 7

[Matthias Versen [:Matti]]

a) You don't need another computer for this (just create an additional test profile)

b) search lines starting with this and delete it (if mozilla is closed! ):
user_pref("dom.disable
(this should kill all enabled blockings)

Ask me if you still have a question and please mark the bug "verified" if it
works for you

-> wfm 

Comment 8

[Max Alekseyev]

I've removed the line with "dom.disable" but that didn't help.
I still see the bug.
Reopening...

Comment 9

[Max Alekseyev]

I've created another account, and everything seems to work now.
How to fix up existing account?

I think the problem should be classified as a bug but related to "bad"
preferences since fix (that is not yet known for me) requiring some manual
cleanup of prefs.js

Comment 10

[Matthias Versen [:Matti]]

The fix is a new profile.
Since we have no support and this itself is no bug (unless you know how to
"corrupt" a clean profile) this is a WFM

Comment 11

[Max Alekseyev]

Ok. Now I know how to corrupt a new profile - just add to prefs.js the line

user_pref("capability.policy.default.Window.focus", "noAccess");

And the bug will show up.
Reopenning...

Comment 12

[Matthias Versen [:Matti]]

no, that is no bug if you add this policy by hand.
It's a bug if you find a setting in the mozilla prefs. for that will not unset it.