I would like to be able to allow either full sites (ie. google.com) or just a subdomain of it (www.google.com). Currently if I set "Strictness" to "Full domain" in the preferences, it doesn't whitelist www.google.com, even though I have google.com in my whitelist.
IMHO a modus-operandi more similar to NoScript would be more useful. In concrete terms:
have the option to show both subdomains and domains in the menu, or only domains
when you whitelist a domain, it should be considered as whitelisting all the subdomains
This is useful, because on some sites I trust the whole site (ie. *.google.com), while on other sites I would like to trust only the particular subdomain (blogs hosted on services like blogger or wordpress come to mind - ie. I would like to trust qwert.blogspot.com but not aoeui.blogspot.com :-)).
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. I like this idea but it has been held up by the fact that I don't have a wildcard system in place yet. So, it's mostly waiting on #8 to provide the underlying functionality, at which point the menu changes are mostly what I envision for #9. Wildcards are the next big feature I'm working on (I have started it, but have been held up by many other things.) Once I get this in place, I'll be looking for feedback about the usability of the menu changes I've made.
I would like to be able to allow either full sites (ie. google.com) or just a subdomain of it (www.google.com). Currently if I set "Strictness" to "Full domain" in the preferences, it doesn't whitelist www.google.com, even though I have google.com in my whitelist.
IMHO a modus-operandi more similar to NoScript would be more useful. In concrete terms:
This is useful, because on some sites I trust the whole site (ie. *.google.com), while on other sites I would like to trust only the particular subdomain (blogs hosted on services like blogger or wordpress come to mind - ie. I would like to trust qwert.blogspot.com but not aoeui.blogspot.com :-)).
The text was updated successfully, but these errors were encountered: