If I activate or deactivate individual services in the popup, the setting does not remain persistent
the switch jumps back to the previous position after a short waiting time
If I activate or deactivate individual services in the popup, the setting does not remain persistent
the switch jumps back to the previous position after a short waiting time
I was able to reproduce this in a fresh LibreWolf install, however it does only occur if you try to set rules without having set any global blocking rules for all pages before.
It's fixed locally on my computer and the fix will be distributed with the next version.
While investigating this, I also found another bug that causes individual page rules not to block anything as long as no global blocking rule is enabled.
This one is not fixed yet but is a high-priority issue that will get fixed for the next release.
I was able to reproduce this in a fresh LibreWolf install, however it does only occur if you try to set rules without having set any global blocking rules for all pages before.
It's fixed locally on my computer and the fix will be distributed with the next version.
While investigating this, I also found another bug that causes individual page rules not to block anything as long as no global blocking rule is enabled.
This one is not fixed yet but is a high-priority issue that will get fixed for the next release.
Niklas Poslovski
If I activate or deactivate individual services in the popup, the setting does not remain persistent the switch jumps back to the previous position after a short waiting time
a browser restart fixed the problem
I was able to reproduce this in a fresh LibreWolf install, however it does only occur if you try to set rules without having set any global blocking rules for all pages before. It's fixed locally on my computer and the fix will be distributed with the next version. While investigating this, I also found another bug that causes individual page rules not to block anything as long as no global blocking rule is enabled. This one is not fixed yet but is a high-priority issue that will get fixed for the next release.
The bug mentioned in my last answer is now fixed, too.