This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@capsizecss/core@4.1.2
Patch Changes
#2006238501 Thanks @michaeltaranto! - createFontStack: Prefer postscriptName or fullName for fallback source
The @font-face declaration aliases generated by createFontStack now favour postscriptName and fullName over familyName from the provided metrics when selecting a local font face as a fallback.
MDN recommends using either fullName and postscriptName when accessing local fonts to ensure the best matching across platforms, while also enabling selection of a single font face within a larger family, e.g. Arial Bold or Arial-BoldMT within Arial.
For details see MDN.
⚠️ Note: Falling back to familyName (original behaviour) makes this work backwards compatible with older versions of font metrics.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@capsizecss/core@4.1.2
Patch Changes
#200
6238501
Thanks @michaeltaranto! - createFontStack: PreferpostscriptName
orfullName
for fallback sourceThe
@font-face
declaration aliases generated bycreateFontStack
now favourpostscriptName
andfullName
overfamilyName
from the provided metrics when selecting a local font face as a fallback.MDN recommends using either
fullName
andpostscriptName
when accessing local fonts to ensure the best matching across platforms, while also enabling selection of a single font face within a larger family, e.g.Arial Bold
orArial-BoldMT
withinArial
. For details see MDN.