46564 - non-resizable popup window can't be closed w/ mouse

Status: VERIFIED DUPLICATE of bug 56165

(SeaMonkey :: General, defect, P3)

Description

[namos]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS 5.8 sun4u; en-US; m17) Gecko/20000725
BuildID:    2000072522

a javascript pop-up window that can't be resized also can't be iconized or
closed with the mouse (at least in cde).  the buttons in the corners of the
title bar are missing

Reproducible: Always
Steps to Reproduce:
1.go to http://www.hkhosting.com/contact.shtml
2.click "why email?" near bottom
3.try and close the window without using the kbd

Comment 1

[Asa Dotzler [:asa]]

this works on win32 mozilla 072608 on NT.  There is an "x" in the top right
corner of the titlebar allowing you to close the window.  I don't have a Sun
Solaris box to test on so adding qawanted and looking for confirmation.

Comment 2

[Michael Hore]

I have no problem on my redhat linux i686 box running m17 who's build id has
been blasted from the face of the bottom right corner.

Comment 3

[Asa Dotzler [:asa]]

the build ID now appears in the titlebar.  Resolving worksforme.  

Comment 4

[Doron Rosenberg (IBM)]

**Mass Spamm**
adding verifyme keyword to all worksforme bugs.

Comment 5

[John Unruh]

Reopening. This is happening on commercial branch Linux build 101109. Setting to 
critical, since this is probably preventing Security Advisor child windows from 
working correctly.

Comment 6

[John Unruh]

Confirming.

Comment 7

[John Unruh]

This is a bug with the commercial branch 101109 Linux build.

Comment 8

[Asa Dotzler [:asa]]

unable to reproduce this problem with 10/11 mozilla branch or trunk linux 
builds.  This has not regressed. This bug was concerned with the missing 
titlebar close control "X" that prevented the user from killing the popup. The 
popup at http://www.hkhosting.com/contact.shtml works just fine.  It has a 
titlebar and close widget.

Comment 9

[Dan M]

John asked me to take a look at this. (By the way Asa: I'm told this is bug only
known to show up on a Netscape rtm branch build, not Mozilla.) Following the
steps given above to reproduce, the website issues a window.open call with this
features parameter:

"width=350,height=350,directories=0,location=0,menubar=0,resizable=0,scrollbars=yes,status=0,titlebar=0,toolbar=0"

As you can see, they're explicitly trying to turn the titlebar off, though not
the closebox. Still, this is very rude, since the window they're creating
contains no "close" button in its content, and the OS close widget is nearly
always located on the titlebar. However, Mozilla is supposed to disallow turning
off the titlebar by unprivileged JavaScript.

So perhaps there's some code change in the affected tree that makes it pay a
kind of partial attention to the titlebar=0 line. To help pin this down, I
suggest someone spend some time with the affected build, opening windows with
various combinations of titlebar/closebar on/off and see what happens.

With unprivileged JS, you shouldn't be able to affect the presence of the
titlebar at all, but you should be able to get rid of the close box. This
experiment is most easily done using the sample XUL source that you can get to
with a debug Mozilla build from the Debug menu -> XPToolkit -> Dialog page.
That's missing from the Netscape builds, so you'll have to grab the source for
that page yourself. You want dexopenchrome.xul and dexparamdialog.* from the
mozilla/xpfe/browser/samples/ directory. Attempt to turn off the titlebar by
leaving the "titlebar" checkbox unchecked, but checking the "explicit" checkbox
next to it.

Again, I'm thinking perhaps this particular build interprets strangely the
"features" parameter used by this website when opening a window. Pinning down
what combination of features would be helpful.

Comment 10

[lchiang]

pschwartau - is this your area to try to narrow down as per above comments?

Comment 11

[Phil Schwartau]

No, I'm afraid not - I'm QA for the standalone JS engine, not the browser.
I'll be glad to help out if needed, however - 

Comment 12

[John Unruh]

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

Comment 13

[Phil Schwartau]

Verifying Duplicate -