Unwanted margin at headers top

[idenisovs]

Hi,

Is it possible to remove unwanted margin at the top of header?

At the moment it look like in the screenshot.

In header.html:

html, body {
    margin: 0;
    padding: 0;
    font-size: 13pt;
}

In PHP:

$request = new HTMLRequest($contentHtml);
$request->setPaperSize(Request::A4);
$request->setHeader($headerHtml);
$request->setFooter($footerHtml);

Gotenber version 6.x

setMargins affects just content.html, header.html still has the margin.

$request->setMargins(Request::NO_MARGINS);

[gulien]

Hello @idenisovs,

Could you try this solution puppeteer/puppeteer#4132 (comment)? If it works, I’ll update the documentation 😄

[idenisovs]

Hi, @gulien! Thanks for you answer! Just tried to apply padding: 0 !important, unfortunately, that solution is not working.

[gulien]

Hmm, did you add the style directly in the header.html file?

[idenisovs]

@gulien Yes, in header.html.

I came to different solution, by setting margin bottom negative value, like that: margin-bottom: -15px;, but anyway, that is strange.

[gulien]

Seems weird but hey, if it works 😅

[neongrau]

Started with trying to figure out the spacing above and below too, then went on to figure out the scaling issue.
As i have some landscape and some portrait PDFs to print i tried to find a general solution and it seems this works regardless of orientation and page size/width.

Note the #header and #footer ids are internally used by chromium.
If you already use these ids in your HTML and CSS for PDF generating you are in for a bad ride.
So get rid of them if you have and add this snippet to your header and footer HTML.

#header, #footer {
  padding: 0 !important;
  transform: scale(0.75) !important;
  transform-origin: top left;
  height: 100% !important;
  position: fixed;
}

While the transform scale alone would just make the width smaller, setting height and position: fixed as well will help render it at the same original width (weird actually, but not complaining) without having to set the width explicitly. At least for me. Maybe it helps the next one running into this issue.

FYI: this all goes back to a chromium bug known since March 2018 but hasn't been fixed until today.
https://bugs.chromium.org/p/chromium/issues/detail?id=818496