AI & Agent Dev Bug Sandbox Back to Radar

AdjustFontFallback=False Ignored For Google Fonts In Next.Js 15

When using next/font/google with adjustFontFallback: false, the generated CSS still includes the automatic fallback font family, causing the fallback to always be applied. This is a regression from Next.js 14.

highConfidence 85%Next.js Affected V15.0.0 Affected V15.1.1-Canary.1

Origin Analysis

In Next.js 15, the Google Font loader fails to conditionally include the auto-generated fallback font when adjustFontFallback is set to false. The generated font-family CSS property always appends the fallback font, regardless of the option.

1. Create a Next.js 15 project (e.g., 15.1.1-canary.1). 2. Import a Google font using next/font/google, setting adjustFontFallback: false. 3. Apply the returned className to the body element. 4. Open browser devtools and inspect the computed font-family on body. 5. Observe that a fallback font family is included even though adjustFontFallback is false.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This inline style may be overridden by other CSS rules with higher specificity or break if inter.style.fontFamily is undefined in certain Next.js versions. It only handles a single font applied to the body; multiple fonts or component-level usage need similar handling. To roll back, remove the inline style and retain the original className. Upgrading to an official fixed version is strongly recommended instead of relying on this workaround long-term.