197856 - window.open opens child window UNDER parent window, rather than OVER parent window

Status: RESOLVED DUPLICATE of bug 192454

(Core :: DOM: Core & HTML, defect)

Description

[C Bass]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312

When calling for a child window with window.open as in the following example
(this example code has been in use for several months now):

<A href="#photos"
onClick='window.open("../resenlarge.cgi?prop=GranthamCape&photo=GranthamCape1","MultWin",
"toolbar,resizable,scrollbars,HEIGHT=400,WIDTH=500")'><IMG
src="./GranthamCape1m.jpg" alt="Photo" align=center width=200 height=121></A>

child window correctly opens OVER parent window in ALL browsers, including
PRE-Versions 1.3 of Mozilla.  In Version 1.3 of Mozilla, child window
incorrectly opens UNDER the parent window.

Reproducible: Always

Steps to Reproduce:
1. Go to URL:  http://www.irenet.com/nh/residential/GranthamCape/
2. Click on photo
3.

Actual Results:  
Child window (enlarged photo) will incorrectly open UNDER the parent window.

Expected Results:  
Child window should open OVER the parent window.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Sounds like the parent raises itself due to the page scroll or something....

Comment 2

[Ere Maijala (slow)]

Could be. I've been working on bug 163372 and I'm beginning to wonder why we
raise windows when focus is changed. I think what happens also here is that when
the image is clicked, the new window is opened, but also the current one moves
to anchor causing some focus call or something. Now it depends only on the order
of these events if the result is correct or not. 

Comment 3

[HARUNAGA Hirotoshi]

this is a dup of Bug 192454.
already fixed on trunk-nightly.

Comment 4

[Johnny Stenback (:jst)]

Mass-reassigning bugs to [e-mail]

Comment 5

[HARUNAGA Hirotoshi]

1.3/WinNT has this problem, but 2003032808 and 2003051214/WinNT don't have.
Marking as dup of Bug 192454.

*** This bug has been marked as a duplicate of 192454 ***