10.1.6.2 Changes and behaviour (incl a bug).
Posted: Sun Dec 31, 2017 3:39 am
Great.
So now we can't change the default settings on domains that are already set to default any more.
If you want to change them (*), you have to go to the options, which do not SHOW any default domains,
then set a domain you already set to a rule for to default,
then change the default settings,
and
then change the domain back to whatever it was.
That surely is more logical and easy to understand than what it was before....
Hurray for UI improvements...
Especially if someone doesn't even know that the default rules are not "run nothing" as one might expect (might, not has to). Finding the default settings now is a pure "prior knowledge" thing. I do not think anybody will find them on their own in this current implementation.
*)Which in itself might not be that bad if not for a bug (possibly related to a bug from the first NS 10 version that was fixed, this is not new in 10.1.6.2).
Back than creating a custom rule with checkmarks changed the default settings with the same checkmarks.
This still happens IF:
You use the insite interface of a missing object or media, and allow it from there.
Example:
http://imagevenue.com/
If you have it completely blocked as default
The flash object will first be complained about by Firefox.
If you allow it, the next is the NS10 field that blocks the flash object.
If you click, a popup will ask you whether you want to trust the file or the domain.
If you choose the domain, it will create a custom rule with "object" set.
And it changes the default rules to allow objects.
Which you now will never see, unless you look in the debug log, or mess with your set rules in the described way.
If you are removing the preset settings from the pop-up for good, could you please at least make a dedicated line above all the specific rules in the options window where all the presets can be seen and configured?
So now we can't change the default settings on domains that are already set to default any more.
If you want to change them (*), you have to go to the options, which do not SHOW any default domains,
then set a domain you already set to a rule for to default,
then change the default settings,
and
then change the domain back to whatever it was.
That surely is more logical and easy to understand than what it was before....
Hurray for UI improvements...
Especially if someone doesn't even know that the default rules are not "run nothing" as one might expect (might, not has to). Finding the default settings now is a pure "prior knowledge" thing. I do not think anybody will find them on their own in this current implementation.
*)Which in itself might not be that bad if not for a bug (possibly related to a bug from the first NS 10 version that was fixed, this is not new in 10.1.6.2).
Back than creating a custom rule with checkmarks changed the default settings with the same checkmarks.
This still happens IF:
You use the insite interface of a missing object or media, and allow it from there.
Example:
http://imagevenue.com/
If you have it completely blocked as default
The flash object will first be complained about by Firefox.
If you allow it, the next is the NS10 field that blocks the flash object.
If you click, a popup will ask you whether you want to trust the file or the domain.
If you choose the domain, it will create a custom rule with "object" set.
And it changes the default rules to allow objects.
Which you now will never see, unless you look in the debug log, or mess with your set rules in the described way.
If you are removing the preset settings from the pop-up for good, could you please at least make a dedicated line above all the specific rules in the options window where all the presets can be seen and configured?
