Subnet whitelisting is not working since I'm running on v10

[sergista]

Ever since I've updated to NoScript version 10 the subnet whitelisting feature does not work anymore. (I think it was when Firefox Quantum was introduced? I don't remember)
Despite it is still listed on the features page

2. Subnet matching - an address with a partial numeric IPv4 IP will match all the subnet. You must specify at least the 2 leftmost bytes, e.g. 192.168 or 10.0.0. Again, matching sites will be temporarily allowed on demand.

I lived with it and patiently waited for a fix (because now I nearly have every IP from 192.168.x.x and 10.x.x.x in my list)
But from time to time I'll have to add another IP and it has just gotten so frustrating during my work as network administrator

I thought about editing the config file and adding every possible IP I could ever face, but that just does not feel right, it has to work the old way
what I did try though: I've removed all private IPs from the config file and just added 192.168 but it did not work either

I am at the point where I use Firefox as my default browser with NoScript and Chrome without NoScript to avoid adding every IP

any hint is much appreciated

thanks
regards

[sergista]

Does nobody have a clue on this?

I've tried it on a newly installed Win 10
installed FF and added NoScript
and it won't work

first I've added 192.168 to the list
but I can't access any IP startig with 192.168
I have to add every IP I'm using


Am I missing anything?
I mean, it should work right?

thank you

[barbaz]

This was apparently fixed at some point - viewtopic.php?p=106119#p106119 and I can confirm it works in NoScript 11.4.11rc2.

Thanks lh61 for the report