Allowing Scripts on HTTP (non-HTTPS)

[modmew8]

Hi there,

I just tried the stable version (and the development version 10.1.2rc1) on Firefox Quantum 57.0 and discovered a behaviour I am not sure wether it is a bug or a feature.

For instance, visit http://junit.org/ click on the NoScript icon and allow the site junit.org permanently. Close the NoScript popup menu (by clicking on the blank page) and toggle it back on. The entry junit.org is again blocked by default.

What happens?
I assume, since junit.org is after this action present on the addon configuration tab, apparently, only HTTPS-content is allowed after clicking in the popup menu.
Same scenario as before, clicking on the NoScript icon, allowing the site, and clicking the green lock icon to make it red, the entry remains unblocked (clicking on the blank page and back into the popup menu).

So visiting a HTTP page with blocking content requires two clicks, first allow and then allow HTTP-content too.
Is this intended behaviour? Or should this click on a HTTP-site already allow HTTP content automatically? (which I believe was the behaviour before Firefox Quantum)

(when reproducing, junit.org redirects using javascript to junit.org/junit5/ - so be sure to switch back to junit.org, since junit.org/junit5/ correctly displays with blocked content too)

Thanks in advance!