This evil site does several things to get in the way of closing it: * Tries to move the window around (bug 144069, bug 186708). * Dozens of alerts in onbeforeunload (bug 391834 would prevent these from appearing; bug 59314 or bug 61098 would let you escape). * Disables keyboard shortcuts such as Cmd+W. Perhaps Firefox should not allow sites to cancel certain keyboard shortcuts.
Then if this website use multiples bugs in Firefox which are already known and have a correct priority, I believe that this bug report should be closed, what do you think about it?
Sure, it could be closed as INVALID, or it could be used as a metabug. We should make sure there's a bug on the keyboard shortcut issue, too.
I like the idea of using this as a meta bug. Transforming for that end. --> Confirmed --> Setting dependencies --> And I'll file the follow on bug for the Cmd W redirect.
Added bug 435501 for the keyboard re-mapping issue.
Clint, here's a bug for the keyboard re-mapping issue: bug 340902 (which was itself a duplicate of older bugs). It's marked resolved but I cannot personally confirm that it is a resolved matter.
Thanks The fact that such problems have been around since 2000 with no fix is enough to kill Fx for me. I will be dropping it and recommending Chrome as the safe web browser from now on.
(In reply to comment #14) > Even blogspot is trapping the browser these days (onclose = "are you sure you > want to navigate away from this page?", though at least it lets you exit). Some of those Events should be ok. Like asking the user if he wants to save (submit) entered text on the page (like a program asking if the user wants to save a file when it closes) So the OnClose Event shouldn’t be kill −9, but more like kill −15 (SIGTERM). (but with an option to just „SIGKILL“ the page, like an app that doesn’t respond to SIGTERM)
My rant about scareware in bug 455078 comment 5 might be relevant.
Safari by default warns you before closing a window where text is entered on a page.
FWIW: I survive www.mylazysundays.com and similar sites thanks to AlertCheck https://addons.mozilla.org/en-US/firefox/addon/13176 This extension does something similar to what's proposed in comment #7 and Chrome's behavior cited in comment #10
(In reply to comment #21) Another extension that solves this problem: RightToClick: https://addons.mozilla.org/en-US/firefox/addon/12572
(In reply to comment #22) A better fix, as the developers here don't seem to care: http://www.google.com/chrome
This bug should be resolved in Seamonkey. I looked at NoScript and AlertCheck. These are too unreliable or tedious, plus problematic updates. Who wants to spend hours learning how to secure a "secure" webbrowser? I disagree with Comment 15. Some kind of verify popup is fine in a program on the user's computer with the user's content, but in the context of the web, where the user does not have control over content, it should never be possible for the user to lose control of the program. Secondly, if NoScript and AlertCheck can be written, then it should be possible for the developers to incorporate the same functionality. I just hope something will be done. Thanks
Awww, still not fixed... Can't we temporary set to false default settings of dom.disable_window_move_resize in about:config like I mentioned in bug #648959 ? Because with this option we have some control. Also Opera and Chrome behave that way too.
(In reply to comment #31) > Awww, still not fixed... > > Can't we temporary set to false default settings of > dom.disable_window_move_resize in about:config I mean set it to true ;p
Yep, I know, but this bugs are VERY OLD. And pasting link to location bar and opening it isn't exactly the popup, because it didn't open any new window. Opera and Chrome have this disabled as I see, so can't we do the same as workaround until some patch with detection of popups will land ? This will prevent us for prank sites without option to close tab/window, because keyboard shortcuts are disabled and all application running from mouse pointer. Odd, that it's still not fixed ;p
Can someone who is more familiar with firefox internals than me comment on https://bugzilla.mozilla.org/show_bug.cgi?id=909615#c10 please? In particular, the user's comment, "The problem is that Firefox works in a totally unexpected way. The user clicked on the tab close button and when a confirmation dialogue appears he expects that this is for confirming the tab close action. I don't see any valid reason for Firefox to disrespect the users wish in this regard. I would be a different thing if the user asked to just close a specific (i)frame but I don't think that Firefox even allows that?"