[Bug]: toHaveScreenshot changes page style and changes font family

[muhammad-saleh]

Version

1.42.1

Steps to reproduce

1. Clone my repo at https://github.com/muhammad-saleh/playwright-screenshot-bug-repro
2. npm install
3. npx playwright test --headed (or headless)

Expected behavior

I expected that the full page screenshot should match the actual page

Actual behavior

I found that at the time toHaveScreenshot is executed, it changes the page styles, and the screenshot has a different font than the actual rendered page.

Running in headed mode, I noticed that the font is properly loaded and rendered, but it's exactly when toHaveScreenshot is executed that this problem happens.

Note: This doesn't happen when I set fullpage: false

Expected font:

Incorrect font in screenshot:

Same behavior also happens in CI with mcr.microsoft.com/playwright:v1.42.1-jammy but it's flaky.

Additional context

No response

Environment

System:
    OS: Linux 6.7 Fedora Linux 39 (Workstation Edition)
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i7-13650HX
    Memory: 22.30 GB / 30.97 GB
    Container: Yes
  Binaries:
    Node: 20.10.0 - /usr/bin/node
    npm: 10.2.3 - /usr/bin/npm
    pnpm: 8.15.4 - ~/.local/share/pnpm/pnpm
  IDEs:
    VSCode: 1.87.2 - /usr/bin/code
  Languages:
    Bash: 5.2.26 - /usr/bin/bash

[yury-s]

Apparently in some cases Chromium triggers font update which interferes with the capturing screenshots. Most likely it is because of this code. The behavior is flaky.

[yury-s]

Investigation notes: after unsuccessful screenshot browser requests the fonts again:

request finished https://tempo.fit/fonts/Moderat/Moderat-Medium.woff2
request finished https://tempo.fit/fonts/Moderat/Moderat-Regular.woff2
request finished https://tempo.fit/fonts/Moderat/Moderat-Regular.woff2
request finished https://tempo.fit/fonts/Moderat/Moderat-Medium.woff2
request finished https://tempo.fit/fonts/Moderat/Moderat-Regular.woff2
request finished https://tempo.fit/fonts/Moderat/Moderat-Medium.woff2
request finished https://tempo.fit/fonts/Moderat/Moderat-Bold.woff2
will screenshot
{
  format: 'png',
  quality: undefined,
  clip: { x: 0, y: 0, width: 1280, height: 3622, scale: 1 },
  captureBeyondViewport: true
}
request finished https://tempo.fit/fonts/Moderat/Moderat-Regular.woff2
request finished https://tempo.fit/fonts/Moderat/Moderat-Medium.woff2

We didn't see such requests in DevTools though.

This was from the following test:

import { test, expect } from '@playwright/test';
import { Page } from "@playwright/test";

export const delay = (ms: number) =>
  new Promise((resolve) => setTimeout(resolve, ms));

test.setTimeout(180000);
test('capture screenshot', async ({ page }) => {
  page.on('requestfinished', (request) => {
    if (request.url().includes('fonts/Moderat'))
      console.log('request finished', request.url());
  });
  await page.goto(`https://tempo.fit`, {
    waitUntil: "networkidle",
  });

  await page.evaluate(() => document.fonts.ready);
  await delay(10000);
  await page.keyboard.down('Escape');
  await page.keyboard.down('Escape');
  await page.keyboard.down('Escape');
  await delay(1000);

  await page.evaluate(() => document.fonts.ready);

  console.log('will screenshot');
  await expect(page).toHaveScreenshot({
    fullPage: true,
    animations: 'allow',
    caret: 'initial',
    scale: 'device',
  });
  console.log('did screenshot');
});

[muhammad-saleh]

@yury-s Thank you for looking into this. Is there a way to prevent Chromium from requesting the fonts again? Any fix or workaround do you recommend?

[yury-s]

No easy workaround unfortunately. You can intercept requests to **/*fonts/Moderat* and abort them but that will change the look of the page.

[Rafiot]

I'm having the same kind of issue and I added (in python) that line before calling the screenshot:

await page.route("**/*", lambda route: route.abort())

But it doesn't seem to change anything. What do you mean by intercept requests?

[muhammad-saleh]

I was able to solve this by this workaround:

1. As @yury-s suggested, I blocked this font family requests
2. In our test code I added the font files
3. In the CI, I copied the font files to the system and cleared the font cache
4. Run the tests
5. Chromium will fallback to system fonts since the font family requests are blocked

[Rafiot]

@muhammad-saleh how did you block the requests?

[muhammad-saleh]

@Rafiot

  test.beforeEach(async ({ context }) => {
    await context.route(/Moderat/, (route) => route.abort());
  });

[Rafiot]

alright, I'll try that again, but it still seemed to get stuck (with the equivalent call in Python).