coltswalker wrote:It shouldn't be difficult to assist.
coltswalker wrote: If developer/coder wants me to try something and report the results here I will.
Also, for security I cannot divulge details about the online banking. Just know it is a common online banking provider that is used all over North America.
guest 54 wrote:I do not use online banking, and this may not help at all, but thought I'd post anyway in case it does. It may be that you need to do the allow globally on the banking site First,
guest 54 wrote: then back out to a blank web page, remove your cookies, and go back to the bank site.
guest 54 wrote:I do with this with hard to get in places.. allow first, and then the site doesn't let me in, back out totally and remove cookies and then go back in. Google maps is one that comes to mind that it occurs with.
Show me a site where Globally Allow is the *only* way to make the page work.
Tom T. wrote:guest 54 wrote:I do not use online banking, and this may not help at all, but thought I'd post anyway in case it does. It may be that you need to do the allow globally on the banking site First,
There is no good reason to Allow Globally *anywhere*. It's there for users who can't be bothered with script permissions, but still want NoScript's protections against clickjacking attacks, XSS, and the many other default protections that remain when Allowing Globally. Typically, a user who is happy with NS has a spouse/parent/child/significant other etc. who doesn't want to take a few minutes to learn to use this vital protection. So NS can remain enabled for them, while the careful user simply unchecks Globally Allow.
Show me a site where Globally Allow is the *only* way to make the page work.guest 54 wrote: then back out to a blank web page, remove your cookies, and go back to the bank site.
Example of a site where this is necessary and successful?
Forbidding third-party cookies is common among privacy-conscious users, and is very strongly recommended by this writer. If they never get set, there is no need to delete them. And again, what would this have to do with logging in to the bank sites that you've never used?guest 54 wrote:I do with this with hard to get in places.. allow first, and then the site doesn't let me in, back out totally and remove cookies and then go back in. Google maps is one that comes to mind that it occurs with.
Huh? I just went to maps.google.com. You can allow (or temp-allow) google.com and gstatic.com, but all you really need are maps.google.com and maps.gstatic.com (fine-tuning permissions). I then planned a trip from Los Angeles, California to New York, New York, and it worked perfectly, including zoom function, etc.
Cookies were *never* allowed. The site works fine.
therube wrote:@guest 54
It certainly could be a cookie related issue, though I would think that simply deleting cookies would suffice, without going through the Allow Globally step.
Verizonwireless.com (vzw.com) is a site where I have found cookies are easily screwed up & in those cases, Allowing, dis-allowing, ... ends up only in frustration. (That parts of their website are flawed doesn't help matters.)
Guest wrote:...It's that gstatic doesn't show as needed until I go back out and come back in. Just ignore my posts..
therube wrote:Well certainly not the *only* way, but on some pages, like the recently visited http://www.washingtonpost.com/opinions/telnaes where it is such a PITA to figure out what is needed (for the video clip), Allow Globally (safety concerns aside) takes a lot of frustration out of the picture. (And it can make it easier to back into the needed combination, at times, too.)
Guest wrote:Hi again Tom,
I do have automatically reload in place. I believe the reason I have to back out for gstatic to show is because google.com is not whitelisted until I go in google maps. Then the page refreshes and gstatic isn't there, so I back out and come back in and then gstatic is there for me to temp enable.
Users browsing this forum: No registered users and 8 guests