Desperately need better HTTPS Everywhere trouble-shooting support
If users cannot figure out which of the HTTPS Everywhere rules is preventing accessing of their web pages, they will quit using it.
Sadly, that is the situation that I am in. My wife is crazy for the Java games at pogo.com. Anything that prevents her from playing them is a show-stopper.
When HTTPS Everywhere prevented her from editing her pogo.com avatar, it was easy to identify the pogo.com rule as the culprit. I disabled that single rule (see Ticket #4735 (moved)) and all is well.
Now there's another pogo.com breakage caused by HTTPS Everywhere (see Ticket #4868 (moved)). I cannot identify which of the hundreds of rules is causing this problem, so they all have to go.
There is absolutely no way I will test disabling each rule individually and attempting to reproduce the problem being observed. And since HTTPS Everywhere only allows enable/disabling rules singly or globally, doing a binary search is not an option.
You guys have got to improve the ability of users to identify which rule(s) are to blame for web content failing to work properly.
Trac:
Username: tmpname0901