[FIXED] Contextual permissions get confused about context on plain-HTTP sites

Bug reports and enhancement requests
Post Reply
barbaz
Senior Member
Posts: 10841
Joined: Sat Aug 03, 2013 5:45 pm

[FIXED] Contextual permissions get confused about context on plain-HTTP sites

Post by barbaz »

If you try to set a contextual permission on e.g. http://forums.mozillazine.org/ NoScript will only offer to set it for "...http://forums.mozillazine.org". This makes no sense, as there is never any component of a URL to the left of its scheme.

On the HTTPS version of forums.mozillazine.org the only contextual permission option offered is for "...mozillazine.org".
*Always* check the changelogs BEFORE updating that important software!
-
User avatar
Giorgio Maone
Site Admin
Posts: 9454
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: Contextual permissions get confused about context on plain-HTTP sites

Post by Giorgio Maone »

Should be fixed in latest development build, thanks.

v 11.3.3rc4
============================================================
x Fixed wrong label for http: sites in contextual policy UI
(thanks barbaz for reporting)
x Fix for first party context policy ignored on first load
in new tabs (thanks ayi for reporting)
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0
barbaz
Senior Member
Posts: 10841
Joined: Sat Aug 03, 2013 5:45 pm

Re: Contextual permissions get confused about context on plain-HTTP sites

Post by barbaz »

Thanks, it shows the full address now 8-)

Looking at the commit, the use of === in this line looks weird, is it intended?
*Always* check the changelogs BEFORE updating that important software!
-
User avatar
Giorgio Maone
Site Admin
Posts: 9454
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: Contextual permissions get confused about context on plain-HTTP sites

Post by Giorgio Maone »

barbaz wrote: Sun Feb 20, 2022 2:52 pm Looking at the commit, the use of === in this line looks weird, is it intended?
A typo (already there), indeed. Fixing it, thanks.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0
Post Reply