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!

ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

how to stop firefox on repeatedly opening new tab on downloads?

  • 4 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 1 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย jscher2000 - Support Volunteer

more options

its annoying how my firefox repeatingly opening new tabs when i open a downloaded file especially an excel file. since i'm downloading tons of excel file a day for my work

its annoying how my firefox repeatingly opening new tabs when i open a downloaded file especially an excel file. since i'm downloading tons of excel file a day for my work

การตอบกลับทั้งหมด (4)

more options

Try to use the right-click context menu and use "Save Link as" if you are currently left-clicking the link. Firefox doesn't know that you want to down;load the file and first opens a new tab.

You can also consider to set this pref to true on the about:config page and hold down the Alt key when left-clicking.

  • browser.altClickSave = true

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.


เปลี่ยนแปลงโดย cor-el เมื่อ

more options

doesnt solve the problem

more options

Firefox shouldn't open a new tab when you use "Save Link As".

Did you try to use this item in the right-click context menu?

How does the server send these files?

Are they opened in the new tab if you left-click or do you get an empty page with the open with download dialog?

more options

Another user reported a "blank tab left behind" problem when downloading MP3 files in this thread: Firefox keeps opening new tabs when I download files. Refreshing Firefox will temporarily halt that, but the problem returns the next day I boot up. A workaround was to disable the multiprocess feature, as described in that thread. Could you test that?