On Tue, Jan 28, 2014 at 10:37 AM, Drake, Brian <[email protected]> wrote:
> I'm only using stable versions for now (but when I'm working on rules, I > do check the Atlas and/or Git for the latest rules). > > I'm not sure whether I we're talking about the same thing here. I can > enable or disable rulesets on the fly just fine, but changing the rulesets > themselves (that is, changing the XML files in the HTTPSEverywhereUserRules > folder, or deleting or adding such files) requires a restart. > Oh, sorry: I misunderstood. I believe the problem may lie in the fact that rules are loaded when the extension starts (?) so it's necessary to restart Firefox before the new/edited rules are recognized. There is no obvious way around that; it may be possible to relaunch the extension loading procedure, but I have no idea if and how it can be done. I believe there is a reason why it's not possible to load rules on the fly (which is what's causing your issue) but I'm not sure; maybe Peter or Yan? P.S. I took a look at components/HTTPSEverywhere.js, it seems just a matter of having a trigger or (maybe better) a button that calls HTTPSRules.init()
_______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
