Some behaviour changes I noticed moving to FF Quantum.
Posted: Thu Nov 15, 2018 4:09 pm
I've been using Noscript on Firefox Quantum for a couple of months now and found the functionality lacking in two areas I've gotten used to working much smoother with the old version of FF.
1) Playing media
Everytime I click on a media file that has been blocked, I have to affirm that I really want to play that file. I get why it's there but the old version had the option to let me play media with a single click after the first dialogue box appearing. Alternatively an option to OK the affirmation dialogue with Enter instead of just the mouse would be nice.
2) Blank white sites
This is particular to Instangram and Pintrest, both are displaying blank white pages upon loading until I at least whitelist the top level site. Which gets annoying quickly in the case of Pintrest since they got sites for each top level domain, plus the constant overlays asking me to sign up/in. All I want is a static wall of pictures or a list of links in the Instagram case.
Obviously this came about how FF handles addons in it's new guise so I'm not sure if that is something that can be addressed on the NoScript front or not. But I figured I might bring it up just in case I'm not the only one who has this issues.
1) Playing media
Everytime I click on a media file that has been blocked, I have to affirm that I really want to play that file. I get why it's there but the old version had the option to let me play media with a single click after the first dialogue box appearing. Alternatively an option to OK the affirmation dialogue with Enter instead of just the mouse would be nice.
2) Blank white sites
This is particular to Instangram and Pintrest, both are displaying blank white pages upon loading until I at least whitelist the top level site. Which gets annoying quickly in the case of Pintrest since they got sites for each top level domain, plus the constant overlays asking me to sign up/in. All I want is a static wall of pictures or a list of links in the Instagram case.
Obviously this came about how FF handles addons in it's new guise so I'm not sure if that is something that can be addressed on the NoScript front or not. But I figured I might bring it up just in case I'm not the only one who has this issues.