by Hermooz » Thu Mar 26, 2020 9:02 am
Hi all. Just got bitten by this same issue.
For the moment I avoided the issue by disabling NoScript entirely on the tab where I keep Outlook365 page open, but I would like to use a custom-tailored rule instead.
The thing is, that even if I check with debug console enabled I don't see any request that's going in some domain other than Office365.com (which was obviously already trusted). In the previous message there's the suggestion to trust live.com and office.com, but since I don't see request going towards those site, why would I do it?
Is there any other way to troubleshoot what's going on when noscript step in?
thanks for any hint, and best regards!
Fabrizio
Hi all. Just got bitten by this same issue.
For the moment I avoided the issue by disabling NoScript entirely on the tab where I keep Outlook365 page open, but I would like to use a custom-tailored rule instead.
The thing is, that even if I check with debug console enabled I don't see any request that's going in some domain other than Office365.com (which was obviously already trusted). In the previous message there's the suggestion to trust live.com and office.com, but since I don't see request going towards those site, why would I do it?
Is there any other way to troubleshoot what's going on when noscript step in?
thanks for any hint, and best regards!
Fabrizio