Closed Bug 9307 Opened 25 years ago Closed 24 years ago

[RFE] ability to say no to window.open

Categories

(SeaMonkey :: UI Design, enhancement, P3)

Product:
SeaMonkey
Component:
UI Design
Platform:
x86
All
Type:
enhancement

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 29346

People

(Reporter: csbooton, Assigned: alterego)

References

(
URL
)

Details

I read the opera has a feature that makes it so that it will disabled allowing
of sites opening new browser windows in your borwser without your permission. I
think that this would be a good feature with opions such as allowing opening of
new browser windows by any means , only allow it with the target command (ie do
not allow it using the javascript window.open command) , and only allow it using
javascript, and do not allow it at all. This may help to alieviate the problem
of uselss popus that people just close without reading.
Summary: [feature request] ability to say no to window.open → [RFE] ability to say no to window.open
Target Milestone: M14
Hmmm, no kidding ...
Bug 858 ( a subset of bug 7380 ) is about extending the 4.x Disable Javascript
to a domain-by-domain basis - there's only a small comment about window.open.
This is about window.open disabling.

I think 858 should be closed as a dupe of 7380 and this left as it is, since it
makes no mention of per-domain disabling which is what 858 and 7380 are about.

The combination of the two would certainly be useful, of course, but that
doesn't make them the same.
858 discusses disabling JS capabilities (including execution) based on a variety
of criteria, which could certainly include a decision of ``never''.

Your comment talks about ``creation of new windows'' but the Summary refers
specifically to window.open.  Do you want to update that?  I should update 858's
summary as well, since it's broadened substantially from the original discussion
of disabling JavaScript per-domain.

I'm quite loathe to close 858, because it contains a substantial amount of good
discussion about the kinds of criteria that we might want to support, and also
references to a possible solution coming from Lucent, though I'm not completely
confident that'll arrive at all, or in time.

The dependency thing is probably the right way to show that they're related,
though it does insinuate some sort of primacy on the part of one of the bugs.
Well I can't speak for the reporter, but I assume that means programatically
creating new windows.  Is there another way to do this with js/dom?

I'm not sure what you mean by primacy.
Status: NEW → ASSIGNED
Assignee: don → alterego
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
*** Bug 14971 has been marked as a duplicate of this bug. ***
In addition to sites using JavaScript, some sites open new browser windows using
attributes like target="_blank" or target="somenewname".  Many users find that
annoying too, so it would be nice if Mozilla had an option to disable it.  (Or,
conversely, to open *all* links in new windows, if that's what the user happens
to prefer.)  Opera has such an option.
QA Contact: leger → csbooton
Component: Browser-General → XPApps
I want a little button in my toolbar, labelled "windows", with a little
icon of a window.  It would normally be greyed out.  Whenver a site wants
to open a new window, either with JS or frames, or whatever, the toolbar
button would enable.  Clicking once would pop the window up.  Clicking and
holding would pop up a menu of windows currently in the queue, much like
the "back" and "forward" buttons.  The maximum queue length would be ten.
Or three, depending on my mood.  That's what I want.
Bug 29346 is very similar to this one, but I don't want to close 29346 because 
it has some other approaches to the problem, and also has lots of votes :)
Dan, I don't really think the open in new window pref thing is related to this
since that is explicitly done by the user.  But it would be good to have a
"always in same/always in new/whatever page says" pref, see bug #15512.
How come this is still M14? M14 is already out!
There is a thread about this in n.p.m.layout...the strict DTD doesn't allow 
TARGET in the A tag...so I can't open in a new window without JavaScript.
Mass moving old milestone bugs to M16
Target Milestone: M14 → M16
This bug seems to be inactive, so marking it as a dup of bug 29346.  According 
to mstoltz in bug 29346, there is code to allow blocking window.open (as part 
of configurable security policies, bug 858) but there's no interface for it yet.

*** This bug has been marked as a duplicate of 29346 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified this bug as a duplicate of bug 29346 and marking as such.
Status: RESOLVED → VERIFIED
As a web user, I have no problem if a new window is opened because I clicked on 
something (whether this happens using JavaScript window.open or TARGET="_blank" 
in an HREF). And as a web author, I've used both of these methods in many 
places and few complaints and many instances of positive feedback. But it drives 
me berserk when something opens a new window as soon as I go to a page (or 
worse, when I'm trying to leave). Can we have a setting to disable window.open 
and window.new *only* if they're used in conjunction with onLoad and onUnload 
event handlers? That's the sort of thing I think a lot of people would like. (I 
know I would.)
[ ] diable popups
[X] disable popups other than current site.
[ ] enable popups


surbush@hotmail.com - thats a good idea. 

Here's what Opera has:

[] Accept pop-up 
windows
[] Refuse pop-up windows
[] Open pop-up windows in background

the "backgrounded' 
windows are typically tabbed, so they're not *quite* as
annoying as pop-unders (:  When you 
select 'Refuse', it ignores both window.open and target="" popup windows. I have seen Flash 
files that have skirted around this before, but I'm unsure how.

Hi !

I like the way, galeon handles unrequested windows.
It has an option to open *ALL* windows in tabs, also if they are requested by
javascript, or bei target=xyz.
If you use this feature, along with "don`t jump to new tabs", unrequested
windows will be opened in new tabs in the backgrounds and they aren`t annoying
anymore....

In fact, this is the only feature why i am using galeon instead of mozilla !

So long,

wys

SirTobi
I downloaded PopUp Stopper (it was free) and couldn't use it with Netscape
because it not only stopped pop ups, it also stopped me from being able to click
on a url in an email message and have it open in a browser window.  Whatever
solution is designed for pop ups, it has to allow windows to be intentionally
opened that way.  Also, I want to be able to click on a link on a website that
has HTML code to open the link in a new browser window, I usually want it to
really do that -- I often want to return to the first site without clicking on
"Back" "Back" "Back"
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.