stan Reporter
	Description • 22 years ago

When you have 2 or more tabbed browser windows and when you have an onUnload
event that fires a window.open the new window pops up.  But when you only have 1
tabbed window the window.open is not opening a new window. There is clearly an
inconsistency.

In our application (my company's) we need to open a new window (the architecture
flow) when a user exits a window (some cleanup and unlocking) but this is not
possible even when the Edit > Preferences > Advanced > Scripts & Plugins > Open
Unrequested Windows is set.  Is there anyway to open a new window when the
onUnload event occurs.  This is really needed for our product in order for us to
support Netscape and Mozilla (and we really want that).

What I suggest is to make this feature consistent and also have an additional
preference to enable 'onUnload Popups' if the user choses to (just like the
onLoad Popups).

Thanks guys for your consideration and help,
Stanley Kubasek

	Jesse Ruderman
	Comment 1 • 22 years ago

window.open was intentionally disabled for non-tabbed windows in bug 33448.

	stan Reporter
	Comment 2 • 22 years ago

So there is no way for me to successfully call window.open on the onUnload 
event?  Can this be enabled manually in my browser? Any settings, preferences 
that will make it possible in my case?

	Joseph R. Dietrich
	Comment 3 • 22 years ago

So why disable window.open() on window.onunload events for closing a window, but
not for closing a tab! After all, the stated reason seems to be because of abuse
by malicious webmasters using "hydra ads" -- but if you browse with many tabs
(like I do), then you have a similar problem.

	stan Reporter
	Comment 4 • 22 years ago

I totally agree with you. They should at least make a preference which you can 
set on your own (like they do with onLoad event). That way a user has an option 
to allow it or not.

	Kai Lahmann (is there, where MNG is)
	Comment 5 • 22 years ago

I would say disable in for tabbed browsing too.

stan: be warned, for the people I know, 9 out of 10 come never back, if a page
has a onunload popup, this is seen as being very inpolite.

	Boris Zbarsky [:bzbarsky]
	Comment 6 • 22 years ago

Confirming bug, in any case.  ccing mitch, since he should be in on this.

We _should_ consider adding an (off by default) pref that allows new windows in
onunload, imo.

	stan Reporter
	Comment 7 • 22 years ago

I think it would do no harm to those that don't need it (since it will be off by
default - like suggested) and for those that need it (like myself, since this is
a requirement for our internal application) would make use of it.

Please make the change since I think it would enhance the functionality of the
browser (at least for some users; and IE is using it by default, anyway). 
Appreciate it, thanks!

	Jesse Ruderman
	Comment 8 • 22 years ago

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

	Dan M
	Comment 9 • 22 years ago

  I argue that this is a duplicate of bug 130719. I'm not closing it as such
because it's arguably not; I'll leave it to the owner.
  Really the issue is that popups can't be opened from a window being destroyed
regardless of the pref's value (see that bug and bug 115969). Closing a tab
doesn't destroy the window, so popups aren't disallowed in this case.

	Jesse Ruderman
	Comment 10 • 22 years ago

I think allowing onunload pop-ups should be a separate, hidden pref that
defaults to off.

	jag (Peter Annema) Assignee
	Comment 11 • 22 years ago

stan, do you have a URL or a testpage you could attach so we can see whether
we've addressed your issue with the fix for bug 130719?

	stan Reporter
	Comment 12 • 22 years ago

I tested this feature on Mozilla 1.2b and this feature works correctly. New
pop-up windows can now be opened onUnload as well as alert() box can be shown
(which is the related bug).  

Also, please do not remove this functionality - preference - from future releases.

Thanks guys!

	jag (Peter Annema) Assignee
	Comment 13 • 22 years ago

danm, dveditz, could this have been "fixed" as a side effect to changes recently
made in those areas of the code?

	Dan M
	Comment 14 • 22 years ago

Yes. This is really a duplicate of bug 130719. It's fixed and we have no
intention of unfixing it.