Этот сайт имеет ограниченную функциональность, пока мы проводим техническое обслуживание для улучшения его работы. Если какая-либо статья не решила вашу проблему и вы хотите задать вопрос, наше сообщество поддержки ждёт вас: @FirefoxSupport в Твиттере и /r/firefox на Reddit.

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

After update homepage loads blank screen instead of yahoo.com

  • 2 ответа
  • 1 имеет эту проблему
  • 2 просмотра
  • Последний ответ от cor-el

more options

About 2 updates back a strange problem started occurring; when I open firefox my homepage no longer loads https://yahoo.com, instead i'm greeted with a blank / empty page. Here are some detailed observations about this problem, other than it being super annoying.

- open firefox just as I have for years to see yahoo, nope, it's a blank screen - If I manually click the Home button, yahoo loads fine at that point. - If I open a 2nd firefox browser window, yahoo loads fine. - If I close firefox and open a fresh window again, blank screen.

I've started with add-ons disable - no change I've refreshed firefox - no change I've uninstalled and re-installed - no change

Interesting though if I open Privacy -> Cookies and Site Data -> Manage Data... and delete my yahoo cookie, the homepage loads ok ONCE the first time only. if I close and re-open, I again get the blank screen. The cookie is back. If I "Manage Permissions..." and block yahoo from creating a cookie, it consistently loads on first run, but then I'm constantly hit with yahoo first run banners, etc. that do nothing because each time it loads it has no cookie.

I'm really interested if this is a firefox issue, or a yahoo issue. This problem never happened until firefox pushed an update a month or two ago, I can use any other browser and load yahoo.com with no problem whatsoever.

Can someone please tell me what is happening????????????????? It's a homepage. Really it can't be that difficult to solve.

About 2 updates back a strange problem started occurring; when I open firefox my homepage no longer loads https://yahoo.com, instead i'm greeted with a blank / empty page. Here are some detailed observations about this problem, other than it being super annoying. - open firefox just as I have for years to see yahoo, nope, it's a blank screen - If I manually click the Home button, yahoo loads fine at that point. - If I open a 2nd firefox browser window, yahoo loads fine. - If I close firefox and open a fresh window again, blank screen. I've started with add-ons disable - no change I've refreshed firefox - no change I've uninstalled and re-installed - no change Interesting though if I open Privacy -> Cookies and Site Data -> Manage Data... and delete my yahoo cookie, the homepage loads ok ONCE the first time only. if I close and re-open, I again get the blank screen. The cookie is back. If I "Manage Permissions..." and block yahoo from creating a cookie, it consistently loads on first run, but then I'm constantly hit with yahoo first run banners, etc. that do nothing because each time it loads it has no cookie. I'm really interested if this is a firefox issue, or a yahoo issue. This problem never happened until firefox pushed an update a month or two ago, I can use any other browser and load yahoo.com with no problem whatsoever. Can someone please tell me what is happening????????????????? It's a homepage. Really it can't be that difficult to solve.

Все ответы (2)

more options

Wow, "See also" apparently works much better than the general search function. If anyone else sees this; apparently if you remove the https://www. from your homepage address and just leave yahoo.com - the homepage loads.

Doesn't make any sense, it's still taking you to the https:// redirect.........................

Guess it'll work until someone can figure out what's going on.

more options

Some recent threads about this issue that offer this same workaround: