Problems with whitelisting in 10.1.2 for non-HTTPS sites
Posted: Sun Nov 26, 2017 2:20 pm
As of version 10.1.2, white-listing sites that are not served through HTTPS is un-intuitive to me. After reading the FAQ on this about how it worked in pre-Quantum versions, it makes sense to me now, but I'm guessing I'm not the only user to be confused by this.
The following are my observations:
* When I manually set the option to allow content from a site that is not using HTTPS, the lock symbol turns green. When I check the list again, my change has been reverted to Default. Presumably because it will not allow content from this site anyway (no HTTPS).
* When I use "Temporarily allow all this page", the same site is now temporarily allowed, but the lock symbol is red, i.e. this option strictly ignores HTTPS.
* If I manually set the option to allow content, then click the lock symbol (green -> red), it sticks as expected.
I can understand if you've decided to protect the user from themselves in this regard, but the problem for me mainly stems from lack of information. Currently, I have no way of seeing if a particular site in the list is served through HTTPS or not, the information is truncated to only show "...webpage.com". So I have to go through it using trail-and-error by first attempting to white-list and if it does not stick, white-list with ignoring HTTPS (if that is my decision).
My request is that, short-term, some type of information is implemented to fulfill either of the following options:
* Provide information about the site so I understand that it is or isn't served through HTTPS. (not perfect as any number of users wouldn't understand immediately what the impact of that information is - but once you understand the functionality it would serve you)
* Notify me when I attempt to white-list a page that it still will not load unless I also change the option for HTTPS. (preferably solution, then I would understand that I would need to make a further decision if I still want to white-list it - this is intuitive design in my opinion)
Finally, let me just state that I still love this tool and am extremely thankful for all the hard work you put into it. I waited patiently for it's release before upgrading to Quantum, just because of how dependent I am on it. You're doing a great job!
The following are my observations:
* When I manually set the option to allow content from a site that is not using HTTPS, the lock symbol turns green. When I check the list again, my change has been reverted to Default. Presumably because it will not allow content from this site anyway (no HTTPS).
* When I use "Temporarily allow all this page", the same site is now temporarily allowed, but the lock symbol is red, i.e. this option strictly ignores HTTPS.
* If I manually set the option to allow content, then click the lock symbol (green -> red), it sticks as expected.
I can understand if you've decided to protect the user from themselves in this regard, but the problem for me mainly stems from lack of information. Currently, I have no way of seeing if a particular site in the list is served through HTTPS or not, the information is truncated to only show "...webpage.com". So I have to go through it using trail-and-error by first attempting to white-list and if it does not stick, white-list with ignoring HTTPS (if that is my decision).
My request is that, short-term, some type of information is implemented to fulfill either of the following options:
* Provide information about the site so I understand that it is or isn't served through HTTPS. (not perfect as any number of users wouldn't understand immediately what the impact of that information is - but once you understand the functionality it would serve you)
* Notify me when I attempt to white-list a page that it still will not load unless I also change the option for HTTPS. (preferably solution, then I would understand that I would need to make a further decision if I still want to white-list it - this is intuitive design in my opinion)
Finally, let me just state that I still love this tool and am extremely thankful for all the hard work you put into it. I waited patiently for it's release before upgrading to Quantum, just because of how dependent I am on it. You're doing a great job!