搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Restoring PARTIAL previous session

more options

While using Firefox today, I had a malware popup (for the curious, this one: https://support.mozilla.org/en-US/questions/1030444#answer-651838) on one of my tabs. The only way to kill the popup was to kill the Firefox process. But now if I try to reopen Firefox and restore my previous session, the tab with the malware is active and unkillable.

I have two windows each with multiple tabs I had as references - tabs that are buried weeks down in my history at the moment. Once upon a time, if Firefox crashed (and/or was killed from task manager's process tab), you'd get the "this is embarassing" version of session restore and that would allow you to not load the offending tab, preserving everything else.

Whatever happened to that feature? Are there any plans or ways to bring it back? In situations like this, it would be supremely useful.

While using Firefox today, I had a malware popup (for the curious, this one: https://support.mozilla.org/en-US/questions/1030444#answer-651838) on one of my tabs. The only way to kill the popup was to kill the Firefox process. But now if I try to reopen Firefox and restore my previous session, the tab with the malware is active and unkillable. I have two windows each with multiple tabs I had as references - tabs that are buried weeks down in my history at the moment. Once upon a time, if Firefox crashed (and/or was killed from task manager's process tab), you'd get the "this is embarassing" version of session restore and that would allow you to not load the offending tab, preserving everything else. Whatever happened to that feature? Are there any plans or ways to bring it back? In situations like this, it would be supremely useful.

所有回覆 (1)

more options

UPDATE: After my fourth or fifth attempt, killing the process resulted in the aforementioned "This is embarrassing" prompt and I was able to kill the offending tab. SUCCESS!

The ability to call this on command would still be SUPREMELY useful. Any tips or plans beyond the "beat the dead horse until it works" strategy?

Adding the ability to view your previous session in a side area of the history (always populated with whatever's in the session.js file, perhaps, and always at top?) would likely work.