System Win10 Pro i7-6600U 2.6GHz 8GB RAM 64-bit x64 processor Browser Name: Firefox Version: 71.0 Build ID: 20191202093317 Update Channel: release User Agent: Mozilla/5.0…
System Win10 Pro i7-6600U 2.6GHz 8GB RAM 64-bit x64 processor
Browser Name: Firefox Version: 71.0 Build ID: 20191202093317 Update Channel: release User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0 OS: Windows_NT 10.0 Launcher Process: Enabled Multiprocess Windows: 1/1 Enabled by default Remote Processes: 7 Enterprise Policies: Inactive Google Location Service Key: Found Google Safebrowsing Key: Found Mozilla Location Service Key: Found Safe Mode: false
I have an Office 365 personal account. When attempting to use FF to log in to One Drive directly -- meaning, I go straight to the One Drive login page via bookmark, and do not attempt to enter One Drive via a "side door" such as a link on Outlook.com -- I encounter significant latency and, often, outright non-responsiveness. Last Pass will not autofill the login credentials; nor can I type them in directly with anything other than crippling latency, if at all. Same latency with password and 2-factor entry. If I am able to survive log-in, One Drive presents significant lag to clicks, often accompanied by fleeting clues in the lower-left corner of the screen, usually involving cryptography such as "waiting for cdn-15 office.net . . . " or something similar. Often the word "Excel" or "Word" will be displayed in one of those messages, but they are so fleeting (and appear to be truncated for display) that I can't capture them completely.
Switching off extensions appears to have no effect. The lag and general unresponsiveness continues.
Interestingly, when I instead log in directly to Outlook (and not One Drive), and then move into One Drive via a One Drive link that is presented in the Outlook waffle button, then One Drive appears to behave promptly and normally. No lag issues that I can determine. (Also, with all FF extensions=true, login and use of Outlook is satisfactory. No problems that I can see).
The Windows One Drive app, which runs on the local system, also appears to function normally. I can see/modify files in my One Drive via the local app. That's groovy, but sometimes you need to see the file system in the web browser.
So I guess that's the workaround: Get access to One Drive by going *through* Outlook. Okay, but why? What's going on? How to fix?