[Bug]: Puppeteer Generated PDF is not same as Chrome Generated PDF

Bug description

Puppeteer PDF is generating pdf (from url) different from chrome. In a single page pdf, chrome pdf is okay and generating a single page pdf. chrome_single_page.pdf But puppeteer is adding a blank page at the end. puppeteer_single_page.pdf

When I have long content and multiple page, chrome is generating the pdf okay. chrome_multi_page.pdf Puppeteer is however adding an extra blank page at the start and content spreads into multiple pages.

puppeteer_multi_page.pdf I am not sure if its a bug or I am doing something wrong here. Puppeteer Code

const browser = await puppeteer.launch({
    headless: true,
    args: [
        '--kiosk-printing',
        '--disable-gpu',
        '--disabled-dev-shm-usage',
        '--disabled-setupid-sandbox',
        '--no-first-run',
        '--no-sandbox',
        '--no-zygote',
        '--single-process',
    ],
});
const page = await browser.newPage();
await page.setViewport({ width: 1366, height: 768});
await page.goto(`${req.body.url}`, {waitUntil: ['domcontentloaded', 'networkidle0']});
const pdf = await page.pdf({
    format: 'A4',
    landscape: false,
    printBackground: false,
    preferCSSPageSize: false,
    margin: {
        top: 20,
        bottom: 20,
        left: 20,
        right: 20,
    }
});
     
await browser.close();

Puppeteer version

^19.2.2

Node.js version

v16.16.0

npm version

8.11.0

What operating system are you seeing the problem on?

macOS

Configuration file

const {join} = require('path');

/**
 * @type {import("puppeteer").Configuration}
 */
module.exports = {
    // Changes the cache location for Puppeteer.
    cacheDirectory: join(__dirname, '.cache', 'puppeteer'),
};

Relevant log output

No response

[OrKoN]

It looks like a regression in Chromium: you should be able to work around it by specifying the following argument when launching puppeteer: --disable-blink-features=LayoutNGPrinting

[dcecile]

The --disable-blink-features=LayoutNGPrinting workaround fixed the issue for me. (Running 19.2.2, had a page incorrectly overflowing.) Thanks @OrKoN!