for my pages I've hardcoded the margins on the Chrome-PDF setup in the designer so they're independent of the body. Pagebreaks in chromium seem to be a bit weird (and will continue to have some annoying little niggles until the LayoutNG project is complete and released so jsReport can use it)

oh, sorry ... misunderstood the problem (my problem was with content inside the page not headers) ... do you have margins setup for the page so it knows where the header/footer should be. Is this Chrome-PDF or Phantom-PDF?

it looks like the problem I had a while back ... having a fixed position to the class ( https://forum.jsreport.net/topic/1355/one-block-of-text-repeats/2 ) was my issue

playing around some more, it looks like the problem may be Sophos anti virus (as well as not liking the .exe Windows runtime, it looks like it might be blocking headless chrome according to some other reports) ... sigh. Time to see if I can persuade out security folks to allow it somehow...!

perfect, thanks!

that actually puts the word .null at the end (replacing with '' just puts .)

inline;filename="Campaign Metrics XXXX l Q3 YYYY - All Segments.pdf".null

In my script I am setting the whole of the file name based on some report parameters:

function afterRender(req, res) {
    res.meta.reportName = ('"Campaign Metrics ' + req.data.clca[0]["campaign"] + " - " + req.data.clca[0]["seg"] + '.pdf"')
    res.meta.contentType = 'application/pdf'
}

but, jsReport is being helpful and adding an extra .pdf

inline;filename="Campaign Metrics XXXX l Q3 YYYY - All Segments.pdf".pdf

doesn't seem to be causing any real problems, but is there anything I should be doing to stop it doing this (or would it just be a low priority feature request to not append file extension if quoted?)

thanks! Have reported to Sophos, though they don't seem overly inclined to do anything about it (shame I'm stuck with it on Corp machines)

My assumption is that jsReport isn't trying to sneakily infect us, but might be good to double check the downloable zip to see why it's being flagged :(

Double checked against some other engines and comes up clean

d'oh ... on the subject of "..made a mistake" ... I'd created the asset with the helpers in, and referenced it as

{#asset common-handlers.js @encoding=utf8}

but ... I had a typo in the filename which was why it wasn't finding it. leaving this here so anyone else trying gets to search and learn from my stupidity ;)