When I'm working in SharePoint Online, a customer site, the entire top bar of my browser disappears
I'm a consultant, and work remotely sometimes, using clients' SharePoint sites. Whenever I am working on a SharePoint Online site, the entire top bar of my browser disappears. I can't access any bookmarks or navigation controls, nothing. When I restart FireFox, it's all still gone, but when I do a restart on the computer, everything is right again. Sometimes, over time, the blank space in the top will start to expand, very slowly. Sometimes it will not show up at all, and everything is fine. Sometimes, like today, it's done it three times, and significantly impacts my productivity.
I can't give version number, but I've downloaded the current version. I'm on Windows 10. I can't give any data other than this, because I can't access it.
選ばれた解決策
Thank you all for the responses. However, merely hitting F11 twice fixed the problem.
Thank you, all, again!
この回答をすべて読む 👍 0すべての返信 (4)
Try to contact the website developer/s about that.
Hi rickhoppe, is it possibly Firefox's "full screen" feature? You can test that theory by pressing the F11 function key to turn full screen on and off. Normally, unless the cursor is in the address bar at the time, the entire toolbar area will roll up.
But it would be odd for full screen to persist between sessions until you restart the system. Hmm.
Does it make any difference whether the window is maximized or resizable? If the top buttons are not accessible, try the window control menu: press Alt+Spacebar to drop a menu from the upper left corner of the window.
It is also possible that the website opens a new window/tab that disables specific features. There are prefs present on the about:config page to prevent website from disabling features.
- dom.disable_window_open_feature.*
You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.
この投稿は cor-el により
選ばれた解決策
Thank you all for the responses. However, merely hitting F11 twice fixed the problem.
Thank you, all, again!