You can still run extensions in "developer mode" if you unzip the .crx, but we do definitely need a better approach to beta-testing things (especially rulesets).
On Thu, Sep 11, 2014 at 10:40 AM, Alexander Buchner <[email protected]> wrote: > On 27.08.2014 19:00, Jacob S Hoffman-Andrews wrote: >> On 08/27/2014 12:15 PM, Alexander Buchner wrote: >>> Ok, this is for Linux. And for a Windows user? >> >> We don't yet have development instructions for Windows user; If >> you're interested in helping with that, it would be very helpful. >> >> We don't currently produce development builds for Chrome, only for >> Firefox. I'm hoping in the not-too-far future to configure out >> Travis CI build to store generated .crx and .xpi files somewhere >> web-accessible to make it very easy to test the latest code and >> rulesets. But I don't have that working yet. If you would like, I >> will build a .crx off master and email it directly to you. >> > > Unfortunately Chrome in Version 37.0.2062.120 m (64-bit) now always > removes locally installed extensions. > So is there no way left to deliver a development version to Chrome users? > > > _______________________________________________ > HTTPS-Everywhere mailing list > [email protected] > https://lists.eff.org/mailman/listinfo/https-everywhere -- Nick Semenkovich Laboratory of Dr. Jeffrey I. Gordon Medical Scientist Training Program School of Medicine Washington University in St. Louis https://nick.semenkovich.com/ _______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
