-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >- rule xyz.xml is a ruleset with 'default_off=...' >- I edit this rule to be active again (including removal of 'default_off=...') and commit/make a pull request to the master branch >- If this commit will be part of some future release, will the rule be active automatically again in the future release?
Yes, for all users that haven't manually enabled or disabled that ruleset, it will become automatically active again in a future release. This is a bit confusing because HTTPS Everywhere stores a persistent preference in Firefox whenever you enable or disable a rule. So if you have enabled or disabled the rule during testing, your Firefox profile will remember that even when you install a new version. You can readily test in a clean Firefox profile, created automatically, like so: ./test.sh --justrun That should open up a Firefox independent of your normal one and you can test that the rule is enabled. For Chromium you can run: ./run-chromium.sh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVJtxQAAoJEKczrZbVKyUhFMUP/26If4+UIF0cZ2OA5984NXTQ keRxdul3Bo5WnR+l7mZt/inr7AxsdTuJ47t1XdrSA98qMG7Kpzk6wFaNFiq1w1PV qNoMUH5mfsnTxyE5VICn5RKIDNtnSWj+H2GKS3946PA+badDi0rCUp9w4bzi1JdW neMpqlNjCtXYe+QZa8jqNeO6tQrBLis4nTBpy8qfdlFcf1clZsm1hHX68se+V0C3 k2IJcuSDNgsWaSXWfTl6Us2moQGpEV9sQgsPJX4H39vTRXamrMa9vBtc33iOPVQ6 bdo+dPgK/td9QtoEjkFKg5ZP74Xarg/ol1dqfvFCyF8EJXqV/wX3OTIoPXGNkg+G 7eXu5T5HzNfonAyqL+5HPIelZVyu55u/LUOT1hrxuXrg9q7J5SUUj0M9RKy2luGb oBDledDkLdjUGDxTEWibxFrG9K4wD7GW7zwMdew2z+30qBhPtQ4KD3kgxWWNBtae J/P5njRRZ3RsAPGFOhNZYNjx8enzblWPd0m73mxuuBFMwvkZHKykUsqPxztqqVQa nC1jSX9vIHCbN1L4iHWFFRxWHdGxlMEXui/pXdl4mHoS86UIfY3XfB4GYzjSFChO 98BWfIEoO8Pv6FA+AkwcDCUuvaFeKcS0/+mkZBT1KMZgqBG0ARiP7OTjEzlN222+ OIj+JJXCxu3eiTYeQO1h =MhS5 -----END PGP SIGNATURE----- _______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
