Firefox Headers & Footers no longer printed with NoScript
Firefox Headers & Footers no longer printed with NoScript
After installing NoScript, I find that my headers & footers no longer print for Firefox. There has not been any change to the Firefox Page Setup (i.e. Headers and Footers are still setup). I am using A4 size paper. How can I get them back with NoScript? I am running Windows 8.1.
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Re: Firefox Headers & Footers no longer printed with NoScrip
When this issue occurs, do you see anything related in the Browser Console? (Ctrl-Shift-J)
(if you don't know what's related, turn off CSS warnings and post everything else you see)
Have you tried Allowing Scripts Globally, if so does that help?
It could also be coincidence that it started when you installed NoScript... as a test, does disabling NoScript (Tools > Add-ons Manager > NoScript > Disable > Yes, remove ALL protections) get it working? If not then this is not related to NoScript.
Let us know, thanks.
(if you don't know what's related, turn off CSS warnings and post everything else you see)
Have you tried Allowing Scripts Globally, if so does that help?
It could also be coincidence that it started when you installed NoScript... as a test, does disabling NoScript (Tools > Add-ons Manager > NoScript > Disable > Yes, remove ALL protections) get it working? If not then this is not related to NoScript.
Let us know, thanks.
*Always* check the changelogs BEFORE updating that important software!
-
Re: Firefox Headers & Footers no longer printed with NoScrip
Thanks. I've found the browser console. There are some interesting things there, which I will post, But, how do I turn off CSS warnings first?
Also, since I've been training NoScript for some months now to do what I want, I prefer not to allow everything globally as a test. It may be something I need to allow, but I'd like to look at other things first.
If I disable NoScript and then enable it again, will it remember what I have allowed or disallowed?
Also, since I've been training NoScript for some months now to do what I want, I prefer not to allow everything globally as a test. It may be something I need to allow, but I'd like to look at other things first.
If I disable NoScript and then enable it again, will it remember what I have allowed or disallowed?
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Re: Firefox Headers & Footers no longer printed with NoScrip
I think CSS warnings are already off (I right clicked CSS tab). Here is what I see in the console browser:
Code: Select all
A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'?
See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise
Date: Sat Dec 05 2015 17:06:22 GMT+1300 (New Zealand Standard Time)
Full Message: null
Full Stack: JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: PendingErrors.register :: line 191
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.completePromise :: line 715
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: Handler.prototype.process :: line 970
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.walkerLoop :: line 813
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.scheduleWalkerLoop/< :: line 747
native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0 <unknown>
A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'?
See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise
Date: Sat Dec 05 2015 17:06:29 GMT+1300 (New Zealand Standard Time)
Full Message: null
Full Stack: JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: PendingErrors.register :: line 191
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.completePromise :: line 715
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: Handler.prototype.process :: line 970
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.walkerLoop :: line 813
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.scheduleWalkerLoop/< :: line 747
native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0 <unknown>
about:blank : Unable to run script because scripts are blocked internally. <unknown>
A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'?
See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise
Date: Sat Dec 05 2015 17:07:23 GMT+1300 (New Zealand Standard Time)
Full Message: null
Full Stack: JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: PendingErrors.register :: line 191
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.completePromise :: line 715
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: Handler.prototype.process :: line 970
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.walkerLoop :: line 813
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.scheduleWalkerLoop/< :: line 747
native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0 <unknown>
about:blank : Unable to run script because scripts are blocked internally. <unknown>
A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'?
See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise
Date: Sat Dec 05 2015 17:08:27 GMT+1300 (New Zealand Standard Time)
Full Message: null
Full Stack: JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: PendingErrors.register :: line 191
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.completePromise :: line 715
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: Handler.prototype.process :: line 970
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.walkerLoop :: line 813
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.scheduleWalkerLoop/< :: line 747
native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0 <unknown>
A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'?
See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise
Date: Sat Dec 05 2015 17:08:42 GMT+1300 (New Zealand Standard Time)
Full Message: null
Full Stack: JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: PendingErrors.register :: line 191
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.completePromise :: line 715
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: Handler.prototype.process :: line 970
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.walkerLoop :: line 813
JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.scheduleWalkerLoop/< :: line 747
native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0 <unknown>
POST
https://safebrowsing.google.com/safebrowsing/downloads [HTTP/2.0 200 OK 390ms]
GET
https://safebrowsing-cache.google.com/safebrowsing/rd/ChVnb29nLWJhZGJpbnVybC1zaGF2YXI4AEACSgwIARCzzwUYtM8FIAFKDAgAEN-2BRjhtgUgAQ [HTTP/2.0 200 OK 109ms]
GET
https://safebrowsing-cache.google.com/safebrowsing/rd/ChNnb29nLW1hbHdhcmUtc2hhdmFyOABAAkoMCAEQta8NGLevDSABSgwIABDM3A0YzdwNIAE [HTTP/2.0 200 OK 94ms]
GET
https://safebrowsing-cache.google.com/safebrowsing/rd/ChFnb29nLXBoaXNoLXNoYXZhcjgAQAJKDAgBEMShDxjGoQ8gAUoMCAAQwpsaGMSbGiAB [HTTP/2.0 200 OK 62ms]
GET
https://safebrowsing-cache.google.com/safebrowsing/rd/ChRnb29nLXVud2FudGVkLXNoYXZhcjgAQAJKDAgBEN7sAhjf7AIgAUoMCAAQqKsDGKmrAyAB [HTTP/2.0 200 OK 78ms]
Last edited by barbaz on Sat Dec 05, 2015 2:44 pm, edited 1 time in total.
Reason: wrap console messages in code tags
Reason: wrap console messages in code tags
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Re: Firefox Headers & Footers no longer printed with NoScrip
Neither Allowing Scripts Globally nor disabling NS should erase your whitelist. If you are at all concerned for any reason, you might as well back up your entire NoScript configuration first, it can't hurt.Renee wrote:Also, since I've been training NoScript for some months now to do what I want, I prefer not to allow everything globally as a test. It may be something I need to allow, but I'd like to look at other things first.
If I disable NoScript and then enable it again, will it remember what I have allowed or disallowed?
NoScript Options > Export (the one on the very bottom, *not* the one unique to the Whitelist panel).
As to the console messages you did it correctly but there is unfortunately no way to tell which if any are related to the problem.
And please post console messsages in code tags in the future (I'll fix it above)
*Always* check the changelogs BEFORE updating that important software!
-
Re: Firefox Headers & Footers no longer printed with NoScrip
Barbaz,It could also be coincidence that it started when you installed NoScript... as a test, does disabling NoScript (Tools > Add-ons Manager > NoScript > Disable > Yes, remove ALL protections) get it working? If not then this is not related to NoScript.
THANK YOU, THANK YOU!!!!
You were right, it was a coincidence that it started when I installed NoScript. I tried disabling NoScript as you suggested and the problem was still there. Turns out that my top and bottom margins had been changed to values that were too small, so that the headers and footers did not display. I've fixed that and now everything works as it is supposed to! I really appreciate your help. I am very glad that you told me my WhiteList entries would still be there after doing the Disable then Enable for NoScript, as I didn't want to have to start over with the training for NoScript!!! Again, thank you very much.
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Re: Firefox Headers & Footers no longer printed with NoScrip
You're welcome! 
Thanks for posting the solution and glad you got it working.
Thanks for posting the solution and glad you got it working.
*Always* check the changelogs BEFORE updating that important software!
-