[HTTPS-Everywhere] Developing rules on Google Chrome

[Peter Eckersley]

The most basic customisation is to say that a rule should be disabled on
Google Chrome.  That's commonly the case because of Chrome's mixed content
blocking (https://trac.torproject.org/projects/tor/ticket/6975), in which case
you should commit a change like this:

https://gitweb.torproject.org/https-everywhere.git/commitdiff/bba002bb44fd7318893b116eb575d37753f0f4fc

There are two things that are changed there: one is the name of the ruleset
(which needs to change in order to ignore past state about whether the user
had enabled or disabled the rule), and the other is the
platform="mixedcontent" attribute, which means "only use this ruleset if the
browser will load mixed content".

If you really wanted a /different/ ruleset on Firefox and Chrome, you could
have two versions of the ruleset, each with different platform attributes.
More info here:

https://www.eff.org/https-everywhere/rulesets#platform


On Fri, Oct 05, 2012 at 11:05:50AM -0300, Fábio Emilio Costa wrote:
> How could I customize rules on Google Chrome?
> 
> -- 
> 
> Obrigado!
> 
> Fabio Emilio Costa                 São Bernardo do Campo - SP - Brazil
> fabiocosta0305 at gmail.com            Linux User #416439(counter.li.org)
> MSN: fabiocosta0305 at gmail.com                          ICQ #:173799674
> Yahoo! Messenger:hufflepuff0305                  Twitter:@HufflepuffBR
> 
> Orkut Profile: www.orkut.com/Profile.aspx?uid=16619557238254357700
> Blog: hogwartslinux.wordpress.com
> "Copie. Seja Legal. Não seja trouxa! Use Software Livre!"

> _______________________________________________
> HTTPS-everywhere mailing list
> HTTPS-everywhere at mail1.eff.org
> https://mail1.eff.org/mailman/listinfo/https-everywhere


-- 
Peter Eckersley                            pde at eff.org
Technology Projects Director      Tel  +1 415 436 9333 x131
Electronic Frontier Foundation    Fax  +1 415 436 9993