Hi,
For a long time I have had NoScript configured so that pages don't reload on permission change. Lately I enabled reload because of the "reload current tab only" option and it's way more fluid this way.
However I often find myself allowing a website only so that it displays correctly for a long read or something mostly passive along those lines. Once the newly allowed page is done reloading I disable Javascript. It helps my CPU and I guess it's not bad for privacy either since the worst attacks rely on computer power and need some time to complete, or just constantly monitor user action. So it makes sense to re-disable JS once the page is displayed properly.
The problem is that "reload current tab only" also reloads page on permission removal, breaking the good display. So is there an option to specify that a tab should only be auto-reloaded when a permission is granted ? If not, would it be problematic to add it as an about:config pref ?
Thanks
Reload current tab *only* on permission granted, not removed
-
Jan
Reload current tab *only* on permission granted, not removed
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Re: Reload current tab *only* on permission granted, not rem
What I do, & its my standard way of dealing with bank websites, is I'll enable JavaScript for the site, open each of my accounts in a tab, then one account or some other page of the site in yet another (throw-away) tab.
I'll disable JavaScript in that throw-away tab, that way all my "regular" tabs still display as wanted.
I'll disable JavaScript in that throw-away tab, that way all my "regular" tabs still display as wanted.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 5.1; rv:34.0) Gecko/20100101 SeaMonkey/2.31
-
Jan
Re: Reload current tab *only* on permission granted, not rem
That's not ideal but it's better than no auto reload at all 
Thanks for the workaround! I'll see if I can get used to it.
Thanks for the workaround! I'll see if I can get used to it.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0