After upgrading either Firefox to v23.0.1 or HTTPS-Everywhere to 3.4.1, the counter besides the addon's button in the navigation bar looks a bit weird. Overlaid partially over the icon itself with an ugly box, see attached screenshot.
Would it please be possible to implement an option to disable the counter, or to make it look nicer? Like Ghostery for example, even though it's not a very popular addon by itself ;-)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
. . . Although it seems like the fix above doesn't affect the counter size, so maybe a separate feature to disable the counter entirely would be useful.
Thankfully the codefix for the extra padding was rather trivial :)
The extra padding was due to the 'toolbarbutton-1' and 'chromeclass-toolbar-additional' treating the XBL binding as the parent, which wasn't required/needed since these classes were already defined in the XBL file. Frankly, XBL sometimes feels like black magic to me.
I underestimated how fast this counter code was going to be merged to stable. I will try to push out an option to disable the counter soon, and once I'm done, I'll see if I can 'beautify' the ruleset counter (depending on how much time I have of course).
I'm super sorry I missed all of this while I was on sabbatical. I feel like this is too obscure a setting to have in the toolbar menu. Either it should be in the "HTTPS Everywhere preferences" XUL window or it should just be an about:config button that people who really care can set.
I was looking at the code for updating the counter and noticed that updateRulesetsApplied calls alist.populate_list, which calls rewrittenURI, which does a lot of work. I don't think we should be calling this every time a user switches tabs. :(
Can you look into making updateRulesetsApplied more lightweight, perhaps with some sort of caching?
No worries. If the toolbar menu might not be the right place, let's go with the about:config option. If enough people make a fuss, we can always add an option in the XUL window.
yan,
Yeah, it occurred to me that alist.populate_list is rather inefficient (I stress tested the code to make sure it wasn't a show stopper). I initially had it cached but ran into issues where the counter might not get properly updated if the website loaded any new sites via javascript that potentially applied more rules.
I do think efficiency here should definitely be improved, and I will look into a better method.