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.
In WebExtensions version for Firefox, only the first-party domain is displayed in the drop-down menu. All the rest of the targets (3rd parties, for instance) are missing.
Whether the rules are actually being applied for the third parties is an outstanding question.
I am wondering if this is not a specific case of a more general issue: HTTPS-Everywhere doesn't display rulesets in the dropdown menu if the page is already loaded over https.
the XPCOM extension lists Google.com Subdomains while the WebExtensions extension lists Google.com Subdomains (complex), Google Images and Google Sorry and Google Videos. It looks like the WebExtensions HTTPS-Everywhere is finding which rulesets are used based on the targets but doesn't take into account the rewrite rules (Google Sorry shouldn't be in there).
Should I open a new issue or do you prefer to reopen this one?
Activity
Bisaloo commentedon May 20, 2017
I am wondering if this is not a specific case of a more general issue: HTTPS-Everywhere doesn't display rulesets in the dropdown menu if the page is already loaded over
https.For example, try visiting http://stackexchange.com and https://stackexchange.com and notice the difference.
Bisaloo commentedon Jun 6, 2017
I am not sure if that's the same issue but on http://ipxe.org/, the WebExtensions add-on displays a ruleset but the legacy XPCOM doesn't.
Maybe #10039 is the same issue after all.
Hainish commentedon Jun 9, 2017
This was indeed the same underlying issue as #10039. Closing.
Bisaloo commentedon Jun 14, 2017
The two extensions still don't display the same list of rulesets.
Test URL (it's SFW).
Google.com Subdomainswhile the WebExtensions extension listsGoogle.com Subdomains (complex),Google ImagesandGoogle SorryandGoogle Videos. It looks like the WebExtensions HTTPS-Everywhere is finding which rulesets are used based on the targets but doesn't take into account the rewrite rules (Google Sorryshouldn't be in there).Should I open a new issue or do you prefer to reopen this one?
Bisaloo commentedon Jun 14, 2017
Another test url where the case described in the opening post of this issue hasn't been fixed: https://www.crcpress.com/EDIT: Ok, I understand the mismatch here. The WebExtensions HTTPS-Everywhere simply didn't display domains blocked by uMatrix.
Hainish commentedon Jun 15, 2017
Your edit applies to both of your last two comments, right?
Bisaloo commentedon Jun 15, 2017
No, only to the last one.
I still think the WebExtensions HTTPS-Everywhere display ruleset only based on the targets and doesn't take into account the exact rewrite rules.