Open Bug 84754 Opened 20 years ago Updated 2 years ago
Assignee: asa → jst
Component: Browser-General → DOM Level 0
QA Contact: doronr → desale
Confirmed; I've seen this when visiting some other site, but the JS code used it the same as was reported. (And it's *patented* to. *&$%*#&*$# spamming bastards!) Doesn't show quite the same behavior with KDE 2.1; the window shrinks to a box a couple of centimeters on a side and moves to the lower right hand corner, and still shows up on the window/task bar, but it looks like IceWM (and problably Windows as well) does just what the vermin were aiming for; a pox upon their house, and I fart in their general direction!
Status: UNCONFIRMED → NEW
Ever confirmed: true
This could be fixed fairly easily by not allowing windows to be opened from the onunload event handler, but this won't be fixed right now unless someone submits a fix.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
Disabling window.open while the user is trying to close a window is bug 33448.
While disabling popups in onUnload() would certainly help, it doesn't strike the heart of the problem, which is the creation of a (somewhat) hidden window that can pop up other windows at a later time. Perhaps "pop-up windows" (defined as windows without the usual set of widgets at the top) should be tied to a parent "browser window" (defined as a window with the usual set of widgets on the top) such that if the browser window is closed, the pop-ups will close too. Having the set of widgets, of course, increases the minimum window size, making the hidden window less hidden.
> The ads don't start popping up until you _leave_ the offending site and then > start clicking on links. Does it really happen, if you click on links on another site, or is that just a coincidence? If the former, this is already a security problem in itself, because links should not be observable cross-site. A simple fix for this would be to force a certain minimum size and to force windows to be on screen, right? (There might already be other bugs about that.) Considering the abuse, I think this is a bug, not an enhancement.
Mass-reassigning bugs to email@example.com
Assignee: jst → dom_bugs
Status: ASSIGNED → NEW
With the popup blocker and the recent checkin for bug 118717, is this fixed? The original example doesn't work for me, with or without with the popup blocker enabled.
Assignee: general → nobody
QA Contact: desale → general
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.