[Unrelated] Outlook (Office365) email issue

[officeuser]

With FF58 and NS10 latest installs, I am experiencing an issue when trying to access outlook mail. Even with the only plug-in as NS the mail inbox won't load (unable to post full error as contains too many URLs and this forum thinks spam). Curiously, the other Office365 sites work (onedrive, calendar, etc)

I've tried deleting all history to clear the cache and cookies etc, but the problem persists. I've Trusted all of the MS likely domains that appear (even manually adding azureedge.net to try and get around the error). However, the problem persists.

Thoughts?

[officeuser]

Here is the error (/ replaced with | so the anti-spam doesn't get alarmed):

cId: EBE4F799BF2A4023A8B923F058C108E4
app: Mail
st: 500
reqid: undefined
wsver: undefined
efe: undefined
ebe: undefined
et: ClientError
esrc: Bootstrap
err: TypeError: p.default(...).UserOptions.ReactOptinSettings is undefined
estack: window.Owa.mail<|g<|t.prototype.render@https:||owamail.azureedge.net|owamail|20171117.02|scripts|owa.mail.js:44:471400
H@https:||owamail.azureedge.net|owamail|20171117.02|scripts|owa.mail.js:15:33893
c|<@https:||owamail.azureedge.net|owamail|20171117.02|scripts|owa.mail.js:15:20289
K@https:||owamail.azureedge.net|owamail|20171117.02|scripts|owa.mail.js:15:34961
window.Owa.mail<|<|Kt<|e.prototype.track@https:||owamail.azureedge.net|owamail|20171117.02|scripts|owa.mail.js:15:57969
c@https:||owamail.azureedge.net|owamail|20171117.02|scripts|owa.mail.js:15:20228
u@https:||owamail.azureedge.net|owamail|20171117.02|scripts|owa.mail.js:15:20180
_renderValidatedComponentWithoutOwnerOrContext@https:||owamail.azureedge.net|owamail|20171117.02|scripts|owa.mail.js:44:44203
_renderValidatedComponent@https:||owamail.az
ts: 21|11|2017 13:05:32|

[officeuser]

After more investigation the problem now persists with a Firefox Reset and starting in Safe Mode, ie no plug-ins at all. So nothing to do with no script!

(although I'm still totally stumped as to why a FF reset and clear all offline content didn't fix it, it was fine up until recently!)



ISSUE NOT RELATED TO NO-SCRIPT