ladybird

Author SHA1 Message Date

Author	SHA1	Message	Date
Tim Ledbetter	2c728abd9f	Tests: Use wider test string in FontFace arraybuffer matching test This test relies on the width of the test font and the fallback font being different to determine whether they matched or not. The `offsetWidth` rounding change introduced in `51c7afdf5f` caused these widths to appear the same, meaning the test failed. This change avoids the issue by using a longer string with a deliberately wide glyph.	2026-04-05 09:19:37 +02:00
Tim Ledbetter	5b584fde1d	LibWeb: Register JS-created FontFace objects for font matching Previously, FontFace objects created via the JS and added to `document.fonts` were stored in the FontFaceSet but never participated in font matching during style resolution. We now store both CSS-connected and JS-created font faces in a unified map on `FontComputer`, keyed by family name, and include them all as candidates in the font matching algorithm.	2026-04-05 00:13:35 +02:00

Tim Ledbetter

2c728abd9f

Tests: Use wider test string in FontFace arraybuffer matching test

This test relies on the width of the test font and the fallback font
being different to determine whether they matched or not. The
`offsetWidth` rounding change introduced in 51c7afdf5f caused these
widths to appear the same, meaning the test failed. This change avoids
the issue by using a longer string with a deliberately wide glyph.

2026-04-05 09:19:37 +02:00

Tim Ledbetter

5b584fde1d

LibWeb: Register JS-created FontFace objects for font matching

Previously, FontFace objects created via the JS and added to
`document.fonts` were stored in the FontFaceSet but never participated
in font matching during style resolution. We now store both
CSS-connected and JS-created font faces in a unified map on
`FontComputer`, keyed by family name, and include them all as
candidates in the font matching algorithm.

2026-04-05 00:13:35 +02:00

2 commits