Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

cant get out of website

more options

Website wont close, "are you sure you want to leave this page" comes up. I click yes and it doesnt respond.

Website wont close, "are you sure you want to leave this page" comes up. I click yes and it doesnt respond.

Избрано решение

This is a new scam, the site is designed to ask that question incessantly until you give up.

Most users end up killing the browser in the Windows Task Manager. At that point, if you restart normally, Firefox will try to load your previous tabs and windows, bringing back the problem. It's frustrating.


I've heard of two workarounds to break the cycle:

  1. Disable JavaScript or
  2. Change the post-crash behavior to present a list of tabs instead of loading them all automatically

Disable JavaScript

(1) In the new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(2) In the search box above the list, type or paste java and pause while the list is filtered

(3) Double-click the javascript.enabled preference to switch it from true to false.

This may or may not affect the already open tab, but when you kill Firefox and restart it, the scripts that prevent you from closing that tab should not be able to run. After closing it, you can go back into about:config and turn JavaScript back on.

Change Post-Crash Startup setting

(A) In the new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(B) In the search box above the list, type or paste sess and pause while the list is filtered

(C) Double-click the browser.sessionstore.max_resumed_crashes preference and enter 0 (that's a zero) and click OK.


Also, please see this thread for more information and a longer-term workaround:

Прочетете този отговор в контекста 👍 0

Всички отговори (1)

more options

Избрано решение

This is a new scam, the site is designed to ask that question incessantly until you give up.

Most users end up killing the browser in the Windows Task Manager. At that point, if you restart normally, Firefox will try to load your previous tabs and windows, bringing back the problem. It's frustrating.


I've heard of two workarounds to break the cycle:

  1. Disable JavaScript or
  2. Change the post-crash behavior to present a list of tabs instead of loading them all automatically

Disable JavaScript

(1) In the new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(2) In the search box above the list, type or paste java and pause while the list is filtered

(3) Double-click the javascript.enabled preference to switch it from true to false.

This may or may not affect the already open tab, but when you kill Firefox and restart it, the scripts that prevent you from closing that tab should not be able to run. After closing it, you can go back into about:config and turn JavaScript back on.

Change Post-Crash Startup setting

(A) In the new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(B) In the search box above the list, type or paste sess and pause while the list is filtered

(C) Double-click the browser.sessionstore.max_resumed_crashes preference and enter 0 (that's a zero) and click OK.


Also, please see this thread for more information and a longer-term workaround: