wppaste
WordPress

wp_print_font_faces( array[][] $fonts = array() )

Since
6.4.0
Source
wp-includes/fonts.php:43
Generates and prints font-face styles for given fonts or theme.json fonts.

Compatibility

WordPress
since 6.4.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$fontsarray[][]optional
The font-families and their font faces. Default empty array. @type array ...$0 { An indexed or associative (keyed by font-family) array of font variations for this font-family. Each font face has the following structure. @type array ...$0 { The font face properties.Default: array()
  • $fontstring

    -family The font-family property.
  • $srcstring|string[]

    The URL(s) to each resource containing the font data.
  • $fontstringdefault: 'normal'

    -style Optional. The font-style property.
  • $fontstringdefault: '400'

    -weight Optional. The font-weight property.
  • $fontstringdefault: 'fallback'

    -display Optional. The font-display property.
  • $ascentstring

    -override Optional. The ascent-override property.
  • $descentstring

    -override Optional. The descent-override property.
  • $fontstring

    -stretch Optional. The font-stretch property.
  • $fontstring

    -variant Optional. The font-variant property.
  • $fontstring

    -feature-settings Optional. The font-feature-settings property.
  • $fontstring

    -variation-settings Optional. The font-variation-settings property.
  • $linestring

    -gap-override Optional. The line-gap-override property.
  • $sizestring

    -adjust Optional. The size-adjust property.
  • $unicodestring

    -range Optional. The unicode-range property. } }

Performance profile

How much work a call to wp_print_font_faces() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Trivial

Touches nothing outside its own arguments.

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
6–15

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 16.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
2

2 places in core call this, so the cost is paid more often than your own code shows.

What one call costs · 4 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_print_font_faces() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always6none
empty($fonts)9::WP_Font_Face_Resolver()
!empty($fonts)12->generate_and_print()
always15::WP_Font_Face_Resolver(), ->generate_and_print()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 16 instructions, 6–15 executed per call, 2 branches. The work does not change between versions.

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Uses · 2

Used by · 2

Source code

function wp_print_font_faces( $fonts = array() ) { 	if ( empty( $fonts ) ) {		$fonts = WP_Font_Face_Resolver::get_fonts_from_theme_json();	} 	if ( empty( $fonts ) ) {		return;	} 	$wp_font_face = new WP_Font_Face();	$wp_font_face->generate_and_print( $fonts );}

Changelog

Introduced in 6.4.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data
Generated from the wordpress-develop 7.1.0 tag, from src/wp-includes/fonts.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.