Hi. After I enabled material design on the extensions page (chrome://flags/#enable-md-extensions) and restarted Chrome 53 beta, I could enable HTTPS Everywhere, despite the error message (which then disappeared).
Regards, Joakim 2016-08-25 17:36 GMT+02:00 Søren Fuglede Jørgensen <[email protected]>: > Hi > > It is hard to say if this is related, but that error message also appeared > https://github.com/EFForg/https-everywhere/issues/6506 in which the user > managed to get rid of the issue but for which the root cause was > unfortunately not explained. > > Best, > Søren > > On Thu, Aug 25, 2016 at 05:21:22PM +0200, Joakim Walldén wrote: > > Hi. > > > > After the update, Chrome 53 beta (on Ubuntu) says that the extension may > > have been corrupted, and disables it. The repair function does not repair > > it. To remove the extension and add it again does not help. > > > > I saw that with the previous version (and the current version of Privacy > > Badger) in Chrome 54 dev (fresh install, also on Ubuntu) too. > > > > Regards, > > Joakim > > > > 2016-08-25 2:38 GMT+02:00 William Budington <[email protected]>: > > > > > There is a new release for HTTPS Everywhere out today. > > > > > > From the changelog: > > > > > > Firefox 5.2.2 / Chrome 2016.8.24 > > > * Ruleset fixes > > > > > > Download from the usual places. > > > > > > _______________________________________________ > > > HTTPS-Everywhere mailing list > > > [email protected] > > > https://lists.eff.org/mailman/listinfo/https-everywhere > > > > > > _______________________________________________ > > HTTPS-Everywhere mailing list > > [email protected] > > https://lists.eff.org/mailman/listinfo/https-everywhere > > _______________________________________________ > HTTPS-Everywhere mailing list > [email protected] > https://lists.eff.org/mailman/listinfo/https-everywhere >
_______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
