You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
We disabled the counter by default in Feb 2016, mainly because it's not informative: It counts rulesets (rather than resources), which is a fairly arbitrary divide since some domain names have many rulesets that potentially apply. It also counts potentially applicable rulesets rather than actually applied rulesets, which means that the extension claims credit on sites it didn't modify at all. Also note that the question "is HTTPS Everywhere potentially active on this site" is independently shown by the icon state: light blue for no applicable rules, dark blue for applicable rules. Though I'll admit that's kinda subtle.
I think the best short-term fix is to go back to hiding by default. Long-term, I think the ideal stat to track would be the number of top-level page navigations upgraded. Since this number would get large over time, it would fit better under the menu than as a notification badge.
Reacted by Hugo Gruson, Bardi Harborow, Aidar Yakupov and patheticcockroach
mainly because it's not informative: It counts rulesets (rather than resources)
I agree, how many rulesets applied depend on how a contributor structured the rulesets. It might not be important to the normal user who never contributed to the ruleset base.
Too confusing.
Actually, I like the "light blue icon" feature instead of "counter". Mainly because whether the extension rewrite something is a boolean information.
I am not sure about how others are using the extensions, but personally I focus more on the web content rather than looking at the behavior of the extensions I have (unless I am a web developer).
because we might run into a dilemma when the user demand a different "font color", "popup background color" even a different "default icon color". I would like to avoid the potential maintenance overhead.
For me, the counter checkbox has the same problem like the block-unencrypted checkbox before (which was fixed already):
The checkbox state is saved between browser sessions, but the actual functionality is reset. If I disable the counter and restart the browser, the checkbox stays disabled, but the counter is there again.
Cookies disabled (whitelisting via FF per-page settings) and JS disabled via uBlock origin (whitelisting via uBO).
@koops76
2017.8.31 - the block unencrypted checkbox is working between browser sessions, but the counter functionality is reset each time (while the checkbox state is saved correctly).
While it may or may not serve as an important indicator, it's not a component that needs to be actively drawing user attention. Extension badges are dark grey by default, and there's no compelling reason for an extension to deviate from that unless it's attempting to indicate an abnormal condition, or something else that otherwise deserves user attention.
I found the green color quite distracting initially as I kept thinking there was some sort of notification. While I've now mostly zoned it out, I find it poor UI design. I'm happy to keep the counter if we can change the color back to dark grey.
I have version 2017.09.12 and I have the same problem as foobar13373: even though the counter is "disabled" according to the add-on's settings, it still show up, which is pretty distracting...
The issue is in Firefox 55.0.3. I also use Vivaldi, and there the counter is properly hidden
Hm, what do you mean the Mozilla bug tracker? Isn't that a place for Firefox's bugs and not extension bugs? (or is there a place there just for HTTPS Everywhere? I can't seem to find it :s)
Note that I also use Ghostery and uBlock, both know how to hide their counters if I ask them to. Only HTTPS Everywhere has issues
Update on my issue: I found out that it doesn't occur in one of my (rarely used) Fx profiles. Trying to figure out what's making the difference... I already tried disabling all other extensions, so it doesn't seem to be an add-on conflict
Activity
jsha commentedon Sep 2, 2017
Ah, thanks for the update! Clearly I'm a bit out of touch. :-) Why was it removed?
cschanaj commentedon Sep 2, 2017
I agree, how many rulesets applied depend on how a contributor structured the rulesets. It might not be important to the normal user who never contributed to the ruleset base.
Actually, I like the "light blue icon" feature instead of "counter". Mainly because whether the extension rewrite something is a boolean information.
See also #12308
cschanaj commentedon Sep 2, 2017
I am not sure about how others are using the extensions, but personally I focus more on the web content rather than looking at the behavior of the extensions I have (unless I am a web developer).
cschanaj commentedon Sep 2, 2017
I prefer to have the user to disable the counter manually in such case. As you might know, I am also against configurable color.
P.S. I wish (at least) the button to disable the counter can be more visible from the popup UI.
cschanaj commentedon Sep 2, 2017
because we might run into a dilemma when the user demand a different "font color", "popup background color" even a different "default icon color". I would like to avoid the potential maintenance overhead.
foobar13373 commentedon Sep 2, 2017
For me, the counter checkbox has the same problem like the block-unencrypted checkbox before (which was fixed already):
The checkbox state is saved between browser sessions, but the actual functionality is reset. If I disable the counter and restart the browser, the checkbox stays disabled, but the counter is there again.
Cookies disabled (whitelisting via FF per-page settings) and JS disabled via uBlock origin (whitelisting via uBO).
foobar13373 commentedon Sep 2, 2017
@koops76
2017.8.31 - the block unencrypted checkbox is working between browser sessions, but the counter functionality is reset each time (while the checkbox state is saved correctly).
bardiharborow commentedon Sep 2, 2017
While it may or may not serve as an important indicator, it's not a component that needs to be actively drawing user attention. Extension badges are dark grey by default, and there's no compelling reason for an extension to deviate from that unless it's attempting to indicate an abnormal condition, or something else that otherwise deserves user attention.
I found the green color quite distracting initially as I kept thinking there was some sort of notification. While I've now mostly zoned it out, I find it poor UI design. I'm happy to keep the counter if we can change the color back to dark grey.
foobar13373 commentedon Sep 3, 2017
@koops76
Sorry, was a typo 13 -> 31 - I already have 2017.8.31
patheticcockroach commentedon Sep 22, 2017
I have version 2017.09.12 and I have the same problem as foobar13373: even though the counter is "disabled" according to the add-on's settings, it still show up, which is pretty distracting...
The issue is in Firefox 55.0.3. I also use Vivaldi, and there the counter is properly hidden
patheticcockroach commentedon Sep 22, 2017
Hm, what do you mean the Mozilla bug tracker? Isn't that a place for Firefox's bugs and not extension bugs? (or is there a place there just for HTTPS Everywhere? I can't seem to find it :s)
Note that I also use Ghostery and uBlock, both know how to hide their counters if I ask them to. Only HTTPS Everywhere has issues
patheticcockroach commentedon Sep 22, 2017
Ok, it's created there: https://bugzilla.mozilla.org/show_bug.cgi?id=1402223
patheticcockroach commentedon Sep 22, 2017
They already closed it: "Please report the issue to the extension author" :s
patheticcockroach commentedon Sep 27, 2017
Update on my issue: I found out that it doesn't occur in one of my (rarely used) Fx profiles. Trying to figure out what's making the difference... I already tried disabling all other extensions, so it doesn't seem to be an add-on conflict
Edit: solved with the latest update
pipboy96 commentedon Mar 28, 2019
Related: #17068
pipboy96 commentedon May 9, 2019
Closed as part of UI rewrite.