The default bug view has changed. See this FAQ.
Bug 432687 (eviltraps)

Protect users from websites that trap them or destroy their experience

NEW
Unassigned

Status

()

Core
DOM
--
critical
9 years ago
2 days ago

People

(Reporter: Saïvann Carignan, Unassigned)

Tracking

(Depends on: 46 bugs, Blocks: 1 bug, {meta, sec-want, ux-control})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [sg:want])

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9b5) Gecko/2008041515 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9b5) Gecko/2008041515 Firefox/3.0b5

There are javascript based websites that are traps which cause Firefox to show nasty content and stop answering user requests. Firefox behavior in these situations is really bad since it obey to the code and stop to listen to the user, it's not possible to close, change the configuration, close the tab or even exit Firefox!

A good example is this website (WARNING, this website shows pornographic content and you will not be able to close it without killing Firefox :

www.mylazysundays.com

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Actual Results:  
Impossible to move/maximize/close the Firefox window, impossible to change the website, impossible to close the tab and impossible to modify the Firefox configuration.

Expected Results:  
Firefox should accept the user request to change the website or to close the website, and should not accept javascript code which cause Firefox main window to run on the screen and refuse the mouse.

Even if it's javascript, it's a major issue that Firefox refuse any user request in these conditions. There is no reason to justify the user losing control over Firefox.

Firefox should really give the possibility to the user to exit this webpage.

Comment 1

9 years ago
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.
Component: Disability Access → General
OS: Linux → All
QA Contact: disability.access → general
Hardware: PC → All
(Reporter)

Comment 2

9 years ago
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?

Comment 3

9 years ago
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.

Comment 4

9 years ago
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.
Status: UNCONFIRMED → NEW
Depends on: 59314, 61098, 144069, 186708, 391834
Ever confirmed: true

Updated

9 years ago
Depends on: 435501

Comment 5

9 years ago
Added bug 435501 for the keyboard re-mapping issue.

Comment 6

9 years ago
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.
Component: General → Tracking
Keywords: meta
Product: Firefox → Core
QA Contact: general → chofmann
Alias: traps
Depends on: 450292

Updated

9 years ago
Alias: traps → eviltraps
Depends on: 448484
Depends on: 458826
No longer depends on: 448484

Comment 7

9 years ago
I just got tricked into visiting this website. Until now I never saw any purpose for the Noscript add-on, but Mylazysundays made me install it.

I still think Firefox should react on such infinite Javascript loops. For example, if a website shows a few alert windows, after three to five of them another popup should show up and ask "This seems to be an infinite Javascript loop. Do you want to abort it? [yes] [no, continue]".

This might be useful for computer illiterate people who have no clue how to use Noscript. Also, is there nobody who knows the webmaster personally to pay him a visit?

Updated

9 years ago
Depends on: 402401
Depends on: 467536
Depends on: 469565

Updated

8 years ago
Depends on: 380637
No longer depends on: 435501
Duplicate of this bug: 476593

Updated

8 years ago
Depends on: 331334
Duplicate of this bug: 476593

Comment 10

8 years ago
google chrome and opera both deal with this issue perfectly.
chrome has a checkbox in the popup diaglog which prevents further dialogs to be created.
opera makes the user's "Close tab" command ABSOLUTE and it overwrites any javascript on the website.

Comment 11

8 years ago
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.
Duplicate of this bug: 481473
Depends on: 481625

Updated

8 years ago
Duplicate of this bug: 489531
Depends on: 377496

Comment 14

8 years ago
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). 

It is a bug that such an event even exists.  Closing a tab should "kill -9" the contents.  It should not post any type of event to javascript on the page or count how many alerts the page has popped.  It should just kill the page completely and instantly, along with all alert dialogs from that page.

Comment 15

8 years ago
(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)

Updated

8 years ago
Depends on: 455078
Whiteboard: [sg:want]
Duplicate of this bug: 519924

Comment 17

8 years ago
My rant about scareware in bug 455078 comment 5 might be relevant.
Duplicate of this bug: 525812
Duplicate of this bug: 416071

Updated

8 years ago
Flags: wanted1.9.2?
Depends on: 530258

Comment 20

7 years ago
Safari by default warns you before closing a window where text is entered on a page.
Depends on: 543531

Comment 21

7 years ago
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

Comment 22

7 years ago
(In reply to comment #21)

Another extension that solves this problem: RightToClick: https://addons.mozilla.org/en-US/firefox/addon/12572

Updated

7 years ago
Blocks: 550196

Updated

7 years ago
Depends on: 550238

Updated

7 years ago
Depends on: 167475, 334426

Updated

7 years ago
No longer depends on: 543531

Updated

7 years ago
Depends on: 424201
Duplicate of this bug: 555396

Comment 24

7 years ago
(In reply to comment #22)

A better fix, as the developers here don't seem to care:
http://www.google.com/chrome

Updated

7 years ago
Depends on: 559598

Updated

7 years ago
Depends on: 369608
Duplicate of this bug: 576030

Updated

7 years ago
Duplicate of this bug: 577334

Updated

7 years ago
Depends on: 578210

Updated

7 years ago
Depends on: 578828
Duplicate of this bug: 586022

Comment 28

7 years ago
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
Depends on: 589166

Updated

7 years ago
Depends on: 597934, 598226, 598246

Updated

7 years ago
Depends on: 599662

Updated

6 years ago
Depends on: 613800

Comment 29

6 years ago
(In reply to comment #28)
We have bug 578828 for what your asking

Updated

6 years ago
Depends on: 616838

Updated

6 years ago
Depends on: 564337

Updated

6 years ago
Depends on: 620615

Updated

6 years ago
Depends on: 635888

Updated

6 years ago
Depends on: 560767

Updated

6 years ago
Depends on: 636374

Updated

6 years ago
Depends on: 502561

Updated

6 years ago
Depends on: 636905

Updated

6 years ago
Depends on: 340021
Duplicate of this bug: 648959
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
(In reply to comment #31)
> Awww, still not fixed...
> Can't we temporary set to true 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.

See comment 1. That pref also has a UI: Tools > Options > Content > Advanced button next to "Enable JavaScript". Popups should be able to resize and move themselves.
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

Updated

6 years ago
Depends on: 565541

Updated

6 years ago
Depends on: 616853

Updated

6 years ago
Depends on: 669107

Updated

6 years ago
Keywords: ux-control

Updated

6 years ago
Depends on: 675574

Updated

5 years ago
Depends on: 602286

Updated

5 years ago
Depends on: 678994

Updated

5 years ago
No longer depends on: 550238

Updated

5 years ago
Depends on: 748198
Keywords: sec-want
Depends on: 763257

Updated

4 years ago
Blocks: 86194

Updated

4 years ago
Depends on: 705617

Updated

4 years ago
Depends on: 856977

Updated

4 years ago
Depends on: 808792
Depends on: 861671
Depends on: 907634

Updated

4 years ago
Depends on: 909020
Depends on: 909615
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?"

Updated

3 years ago
Depends on: 934083

Updated

3 years ago
Depends on: 947518

Updated

3 years ago
Depends on: 950336
Depends on: 956524

Updated

3 years ago
Depends on: 1003967

Updated

3 years ago
Depends on: 1046022

Updated

3 years ago
Depends on: 1054966

Updated

2 years ago
Depends on: 1107771

Updated

2 years ago
Depends on: 1117342
Depends on: 1116977
No longer depends on: 1117342
No longer depends on: 934083
No longer depends on: 909020

Updated

2 years ago
Depends on: 1125285

Updated

2 years ago
Depends on: 1131187

Updated

2 years ago
Depends on: 510185
Depends on: 1167023
Depends on: 1169918
Depends on: 1180976

Updated

2 years ago
No longer depends on: 1169918

Updated

2 years ago
Depends on: 685828
Depends on: 1173831
Depends on: 1206411

Updated

2 years ago
Depends on: 1205678
No longer depends on: 1206411
Depends on: 1208825
No longer depends on: 1205678
Depends on: 1208950
Depends on: 676975
Depends on: 839470

Updated

a year ago
Depends on: 1234842
Depends on: 1238692

Updated

a year ago
Depends on: 682569

Updated

a year ago
Depends on: 682565

Updated

a year ago
Depends on: 1246773

Updated

a year ago
Depends on: 1199934
Depends on: 1241048

Updated

a year ago
Depends on: 1260612

Updated

a year ago
Depends on: 1263100

Updated

11 months ago
Depends on: 1270444
Depends on: 1272644
Flags: wanted1.9.2?
Depends on: 1276539

Updated

10 months ago
Depends on: 1278736
Component: Tracking → DOM
QA Contact: chofmann
Summary: Protect users from Javascript trap websites → Protect users from websites that trap them or destroy their experience
Depends on: 1290834
Depends on: 1310659

Updated

5 months ago
Depends on: 1312243
Depends on: 1317573
Depends on: 1316798
Depends on: 1329465
Depends on: 1332590

Updated

23 days ago
Depends on: 1340634
Depends on: 1344490
Depends on: 1346123
You need to log in before you can comment on or make changes to this bug.