After using Facebook for a while a grey seethrough screen comes up and covers the window which prevents me from posting anything, but I can still scroll up/down
A Grey see-through screen covers my Facebook open window preventing me from posting, but I can still scroll up and down. Reloading the page solves the problem for a couple of minutes before repeating the procedure. Problem only experiencing with Facebook Page at this time.
Ọ̀nà àbáyọ tí a yàn
Hi Hannesdp,
Thank you for your question. At this time your question has been escalated to the help desk and in order to investigate the issue I will need a little more troubleshooting information.
First please try to access the page in a private window, then please try to reproduce the issue in Safe Mode, if it is not reproducible in Safe Mode then one of the extension or pug ins may be affecting the scripts on this page.
'Try Firefox Safe Mode to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.
(If you're not using it, switch to the Default theme.)
- On Windows you can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
- On Mac you can open Firefox 4.0+ in Safe Mode by holding the option key while starting Firefox.
- On Linux you can open Firefox 4.0+ in Safe Mode by quitting Firefox and then going to your Terminal and running: firefox -safe-mode (you may need to specify the Firefox installation path e.g. /usr/lib/firefox)
- Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.
Once you get the pop-up, just select "'Start in Safe Mode"
If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.
To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.
A screenshot of the issue and a js console capture may also be needed if the issue persists in a private window. These are the two tools for reference that I can elaborate on as well. [Console tool] [Logging]
And if any other contributors have any other troubleshooting ideas or input please do not hesitate. We are all happy to help!
Ka ìdáhùn ni ìṣètò kíkà 👍 1All Replies (1)
Ọ̀nà àbáyọ Tí a Yàn
Hi Hannesdp,
Thank you for your question. At this time your question has been escalated to the help desk and in order to investigate the issue I will need a little more troubleshooting information.
First please try to access the page in a private window, then please try to reproduce the issue in Safe Mode, if it is not reproducible in Safe Mode then one of the extension or pug ins may be affecting the scripts on this page.
'Try Firefox Safe Mode to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.
(If you're not using it, switch to the Default theme.)
- On Windows you can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
- On Mac you can open Firefox 4.0+ in Safe Mode by holding the option key while starting Firefox.
- On Linux you can open Firefox 4.0+ in Safe Mode by quitting Firefox and then going to your Terminal and running: firefox -safe-mode (you may need to specify the Firefox installation path e.g. /usr/lib/firefox)
- Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.
Once you get the pop-up, just select "'Start in Safe Mode"
If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.
To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.
A screenshot of the issue and a js console capture may also be needed if the issue persists in a private window. These are the two tools for reference that I can elaborate on as well. [Console tool] [Logging]
And if any other contributors have any other troubleshooting ideas or input please do not hesitate. We are all happy to help!