Open Esoppant opened 6 years ago
Oh no, that's no good. How frequently does it happen?
I don't think #17 should affect loading. Something like 38d8f567bb7f8312000f2e8e2999b7a7c35df860 might but that landed a few weeks ago.
Also, I don't suppose there are any errors if you open up the DevTools console? (Or the Browser Console if you know how to open it.)
Same issue it's happening to me. I'm using Firefox Quantum version 61.0
Oh, sorry to hear that. Let me see what I can work out next week. In the mean time the following information would help:
privacy.resistFingerprinting
set to true or any add-ons that might set it or do something similar?Sorry for the delay. Answering for my part:
It happens only some times, in fact, I haven't noticed it since 4 days ago (though it happened multiple times that day).
I start the browser with Rikaichamp active; the inactivation/loading mode trigger happens during the course of my browsing
In the web console, there are various different errors/messages in different websites, but I don't see one that seems to be related to Rikaichamp. Most of them usually seem to be originating from the NoScript add-on I am using.
The Browser Console seems to have the same errors with more details. It's stuff like: "Loading failed for the Githubissues.
Since a few days ago (possibly after around the time this issue was fixed/closed) Rikaichamp tends to go into this loading mode (with its panel icon background faintly blinking grey) that lasts indefinitely. It goes back into working mode after a restart of Firefox. I couldn't find out what the trigger is, but I thought I'd leave this here.