Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

facebook

  • 3 antwoorden
  • 1 heeft dit probleem
  • 16 weergaven
  • Laatste antwoord van cor-el

more options

facebook page won't load, cleared history, cache, downloaded latest version, says I am connected, but loading shows 80% and is just a blank page? All other pages load just fine?

facebook page won't load, cleared history, cache, downloaded latest version, says I am connected, but loading shows 80% and is just a blank page? All other pages load just fine?

Alle antwoorden (3)

more options

Hi dayak, we are getting a lot of reports today of the Facebook main page (new feed) not loading. I haven't noticed a problem on Windows, but I also hardly ever use Facebook, so if the problem only affects frequent users, perhaps that explains the difference.

Do other pages on the site load for you, such as:

more options

Hi dayak, have you tried clearing cookies and site data for Facebook? A simple way is:

In a regular (non-private) window, while viewing the blank Facebook page, or the login page:

Click the lock icon at the left end of the address bar. After a moment, a "Clear Cookies and Site Data" button should appear at the bottom. Go ahead and click that.

In the dialog that opens, you will see one or more matches to the current address so you can remove the site's cookies individually without affecting other sites.

Screenshot attached for reference.

Then try reloading the page. Any improvement (after logging in again)?

more options

This could be a problem with corrupted local storage and possibly running this command in the Web Console to clear storage as posted in bug 1569296 might fix it.

  • localStorage.clear()

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)