This just doesn't make sense, if someone sets it to custom it'll revert on launch. I'm confused by the comment, why doesn't/wouldn't it stick? Do the child prefs not apply when using defaultPref? It's pretty annoying for debugging to have this happen.
cfg: change etp from pref to defaultPref #83
brian6932/settings:cfg/change-etp-from-pref-to-defaultPref into master
We "soft-lock" the ETP pref to prevent users from inadvertently disabling partitioning by setting the ETP pref to custom. This FAQ entry goes in a bit of detail on that.
It's pretty annoying for debugging to have this happen.
What exactly are you trying to achieve? If you want to check if ETP is causing a specific breakage, you can just use the shield icon in the address bar.
Last time I checkded the pref didn't apply when using defaultPref.
What exactly are you trying to achieve?
Sometimes certain parts of etp's blocking can break stuff, and I'll disable those (usually temporarily), while keeping the rest of etp active. This also lets you narrow down the cause, and then report the issues to bugzilla.
- librewolf.cfg
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?