jambon wrote:
4. That https match setting doesn't seem to work properly. I have to disable it on every https site or else the site won't even load properly. I'm not even sure why that's a thing, generally a site is either https or http sitewide and whether it is or isn't has no weight on my decision to enable or block scripts.
That is decidedly not the case. Many sites are a hodgepodge of the main site either http OR https (or providing BOTH) and all the embedded scripts being "whatever" at any given point. That's basically why the option is "only https" or "both" for root matching (which basically the ...site rules are)
"Https only" is an option, because a user might (should!) want to be stopped when they accidentally or via a bad link land on the unencrypted site without having explicitly chosen so. Instead of the https counterpart they usually go to. Just setting aside malfeasance and resulting man in the middle attacks.
This is also not an issue for specific domain matching (back in 1.3c1) which just outright shows you what you are allowing either way.
1. I can't login to Stripe. It keeps saying that Javascript is disabled even when I have allowed everything globally. My whitelist carried over when I upgraded and I could access the site fine previously. Now with the new version though I can't.
Then feel welcome to visit the support forum. We spend quite a lot of time troubleshooting what is specifically wrong. And finding out whether you misconfigured something due to a misunderstanding, or whether the config got borked and whether it can be fixed without reseting the config.
2. Even with scripts allowed globally Noscript still shows numbers signifying that scripts have been blocked but nothing is shown in the dropdown.
See 1. Check the explicit rules in the debug log (in the options), a good first test is also just to create a secondary profile (firefox -p) to check whether it is a borked config or an actual bug (I know, bugs a week after a forced full rewrite!)
3. The interface is not intuitive and it required more interaction than previously. It used to be 1 click to open the menu, 1 click to temporarily allow. (2 clicks total). Now it's 1 click to open the menu, 1 click to whitelist, 1 click to select temporary whitelist (in SUPER tiny icon), then 1 click to disable the https match thing. (4 clicks)
I'll just never understand peoples obsession to fix and redesign stuff that isn't broken. I think trying to do a full redesign at the same time as porting over to FF57 was a bad idea. Would have been better to just get a verbatim copy working on 57 then look to do updates/redesigns and enhancements.
[/quote]
On the other hand you gain a lot of specific fine graining concerning WHAT you actually allow at any given time (especially with sub domain filtering being back in 1.3c1, (although temp custom rule is currently bugged, which throws a bit of a wrench in some of the customizing))
And the interface isn't less intuitive really, because Noscript was not very intuitive for the layman either. Don't confuse years of convention with the initial deep end you have deleted from memory.
for the last bit, the operative phrase being "that isn't broken". Except it was broken. It not being available from the browser IS being broken.
It wasn't a bad idea, it was a "no choice" scenario. Which also explains the missing feature. You can't implement features that the API you need isn't done yet by the provider.
But again "welcome to the support forum, where we distinguish "what you don't like" from "what is actually broken"".
The more actual info you give us, the quicker we find what actually ails you.