This thread was archived. Please ask a new question if you need help.
firefox yahoo mail tab closes after opening download dialog
Hi, For about the last month or so, the Yahoo mail tab closes itself after I click on an email attachment to open the download dialog box. This happens exactly 30 seconds after clicking on the attachment, whether or not I go on to open or save the attachment. It does not happen if I merely 'preview' the image. I don't know if all attachment types behave the same, but it applies at least to jpg and pdf files. The tab can be reinstated via History/Recently closed tabs.
Firefox does not crash, and there are no crash reports. In other respects this is similar to a previous post by 'eladopoulos' on 4/30/22, 8:17 AM (https://support.mozilla.org/en-US/questions/1375635).
Using Safe mode makes no difference. I had set browser.download.improvements_to_download_panel to False, but reseting to True makes no difference. Thanks in advance.
All Replies (2)
It's clear that opening the Yahoo Home page as one of the Firefox 'Home' tabs, then manually going to the 'Mail' page, does work. So how is it that Home tab "https://uk.yahoo.com/" is different from Home tab "https://mail.yahoo.com/d/folders/1?.intl=uk&.lang=en-GB"? What is Firefox taking from the latter URL that causes the subsequent download crash sequence?
Web page scripts are allowed to close a tab under restricted circumstances based on how they were opened. It could be that the difference in the subdomain (uk vs. mail) is a factor in why that opening method immunizes the mail tab from being closed. This is all under the covers and hard to observe.
Thanks, jscher2000. You may be onto something there. I tried testing this by trying alternative 'uk' and 'mail' subdomains when specifying my Firefox Home tabs setting, but I didn't get a working Mail page. So I am stuck with the two-step process to access Yahoo mail. (MS Edge doesn't have the problem; I haven't tried other browsers.) I'll leave this open for a little while in the hopes of inspiration, and as the issue arose only a month or so ago maybe another update may (randomly) fix it in the near future.