We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Restore blank page as "previous session"?

  • 6 답장
  • 1 이 문제를 만남
  • 6 보기
  • 최종 답변자: Ander

more options

If you close FF with just a blank page, and Startup set to "Restore previous session", it should start next time with a blank page, right?

That's what I thought. It doesn't, though; it opens the last NON-blank page you viewed, whatever it was. Is this intentional, or an oversight?

I've set my Home page to about:blank. When I'm finished viewing pages, I'd like to be able to click Home, exit FF, and see that blank page next time. Any way to do that? Or is it a kind of Catch-22 that FF's devs have no plans to change?

If you close FF with just a blank page, and Startup set to "Restore previous session", it should start next time with a blank page, right? That's what I thought. It doesn't, though; it opens the last NON-blank page you viewed, whatever it was. Is this intentional, or an oversight? I've set my Home page to about:blank. When I'm finished viewing pages, I'd like to be able to click Home, exit FF, and see that blank page next time. Any way to do that? Or is it a kind of Catch-22 that FF's devs have no plans to change?

모든 댓글 (6)

more options

What th'...?? I just re-tried what I described—and this time it worked! I'm baffled.

Maybe a certain number of tabs must be open in the window, then closed, before exiting. I'll experiment. Sheesh, though, doesn't it just figure? LOL

글쓴이 Ander 수정일시

more options

Okay, it does definitely happen—just not every time. Weird.

more options

It is possible that you need to wait a few seconds before closing Firefox to ensure that the sessionstore files get updated.

See also this pref on the about:config page.

  • browser.tabs.closeWindowWithLastTab

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

more options

There's up to a 15 second delay before changes are recorded to your session history file. So it could be a difference in timing between your tests.

more options

jscher2000 said

There's up to a 15 second delay before changes are recorded to your session history file. So it could be a difference in timing between your tests.

And just in case you wanted to see where that is set:

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

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

The browser.sessionstore.interval preference sets the maximum time Firefox will wait before updating your session history file, in milliseconds. So:

  • 15000 = 15 seconds (default)
  • 30000 = 30 seconds
  • 60000 = 60 seconds

The default value should work for most people. You might increase the value if you encounter performance issues such as Firefox using too much hard drive in the Windows Task Manager, or if you have read scary articles about wearing out an SSD and you want to reduce wear and tear. However, then there's more of a chance of missing new tabs or changed pages at your next startup (or during crash recovery).

more options

Thanks for your replies.

cor-el said

It is possible that you need to wait a few seconds before closing Firefox to ensure that the sessionstore files get updated. See also this pref on the about:config page.
  • browser.tabs.closeWindowWithLastTab ...

Interesting! Delay before exit doesn't seem to affect the issue, but I don't think it matters. Rather than clicking Home to set the last tab to about:blank, I'll just close it (Ctrl+W) before exiting FF. With browser.tabs.closeWindowWithLastTab set to False (which I see is the default), this leaves FF with a new blank tab, which it seems to remember.