Webfonts: Add internal-only theme.json webfonts handler - WP 6.0 stopgap #40493

hellofromtonya · 2022-04-20T22:42:37Z

Part of #40472.

Props to @aristath who pulled together the key elements of this PR.

What?

Using the Webfonts API from PR #37140, this PR adds a theme.json webfonts handler (albeit funky design) to:

handle only theme.json webfonts defined in fontFace.
prevent access to the webfonts handling mechanisms by encapsulating all logic into one function that serves as a private container, i.e. _wp_theme_json_webfonts_handler().

This is a stopgap approach.

Why?

See the issue for the reasons.

How?

It uses the Webfonts API from PR #37140 but smushes the code together into $fn = function() {} closures that are nested inside of a global function. This global function is the container that prevents access to the handler, thus ensuring the mechanisms are hidden and not accessible for extenders to interact with the handler.

Testing Instructions

Set up instructions:

Using Twenty Twenty-Two theme, either:

Option 1: Download Twenty Twenty-Two's new style variations Twenty Twenty-Two: add alternate style variations wordpress-develop#2440
Option 2: Modify the current version in WordPress Core by:
- In its functions.php file, comment out lines 58 and 81 (the lines that are add inline styles using the font face styles).
- Replace the fontFamilies in its theme.json file

			"fontFamilies": [
				{
					"fontFamily": "-apple-system,BlinkMacSystemFont,\"Segoe UI\",Roboto,Oxygen-Sans,Ubuntu,Cantarell,\"Helvetica Neue\",sans-serif",
					"name": "System Font",
					"slug": "system-font"
				},
				{
					"fontFamily": "\"Source Serif Pero\", serif",
					"name": "Source Serif Pero",
					"slug": "source-serif-pero",
					"fontFace": [
						{
							"fontFamily": "Source Serif Pero",
							"fontWeight": "200 900",
							"fontStyle": "normal",
							"fontStretch": "normal",
							"src": [ "file:./assets/fonts/SourceSerif4Variable-Roman.ttf.woff2" ]
						},
						{
							"fontFamily": "Source Serif Pero",
							"fontWeight": "200 900",
							"fontStyle": "italic",
							"fontStretch": "normal",
							"src": [ "file:./assets/fonts/SourceSerif4Variable-Italic.ttf.woff2" ]
						}
					]
				}
			],

How to Test

How to Test on the front-end

Activate TT2
Load the site's home page in the browser.
In the browser, right click to open the dev tools UI and then select "Inspect" menu item.
In the HTML inspector, open the <head> element to view all of the nodes within the head.
Search for the <style> element that has an ID of wp-webfonts-inline-css.
Open that element.

Expected Results:
The <head> should have one instance of the following HTML style element:

<style id="wp-webfonts-inline-css">
@font-face{font-family:"Source Serif Pro";font-style:normal;font-weight:200 900;font-display:fallback;src:local("Source Serif Pro"), url('/wp-content/themes/twentytwentytwo/assets/fonts/source-serif-pro/SourceSerif4Variable-Roman.ttf.woff2') format('woff2');font-stretch:normal;}
@font-face{font-family:"Source Serif Pro";font-style:italic;font-weight:200 900;font-display:fallback;src:local("Source Serif Pro"), url('/wp-content/themes/twentytwentytwo/assets/fonts/source-serif-pro/SourceSerif4Variable-Italic.ttf.woff2') format('woff2');font-stretch:normal;}
</style>

This element should have

2 @font-face declarations to match what was defined in the theme.json file.
The url should no longer have the file:./ placeholder in it.

How to Test in the back-end

Go to "Appearance" > Themes and make sure TT2 is activated.
Go to "Appearance" > Editor (beta) to load the site editor.
In the browser, right click to open the dev tools UI and then select "Inspect" menu item.
In the HTML inspector, open the <head> element to view all of the nodes within the head.
Search for the <style> element that has an ID of wp-block-library-inline-css. Open that element (see Expected Results for the CSS).
In the Network tab, select "Disable Cache" and "Fonts".
Refresh the page. Notice the font file(s) that are loaded.

Expected Results:
The <head> should have one instance of the following HTML style element:

<style id="wp-block-library-inline-css">
@font-face{font-family:"Source Serif Pro";font-style:normal;font-weight:200 900;font-display:fallback;src:local("Source Serif Pro"), url('/wp-content/themes/twentytwentytwo/assets/fonts/source-serif-pro/SourceSerif4Variable-Roman.ttf.woff2') format('woff2');font-stretch:normal;}@font-face{font-family:"Source Serif Pro";font-style:italic;font-weight:200 900;font-display:fallback;src:local("Source Serif Pro"), url('/wp-content/themes/twentytwentytwo/assets/fonts/source-serif-pro/SourceSerif4Variable-Italic.ttf.woff2') format('woff2');font-stretch:normal;}
</style>

This element should have

2 @font-face declarations to match what was defined in the theme.json file.
The url should no longer have the file:./ placeholder in it.

Design Considerations

To enable testing, this PR comments out loading the Webfonts API files in the lib/load.php file. In doing so, this makes the PHPUnit tests fail as those files are missing.
A mechanism is needed in Gutenberg to continue developing, testing, and maturing the Webfonts API.
- This PR currently hooks _wp_theme_json_webfonts_handler() into 'wp_plugins' action event, giving Gutenberg's plugin the opportunity to remove that callback and load its files.
- Another way to accomplish this is to create a short-circuit within the container. In doing that, the container could be an unnamed static closure registered to the 'wp_plugins' action event. Doing this would eliminate deprecating the function once the Webfonts API is merged into Core.

hellofromtonya · 2022-04-20T23:25:14Z

lib/load.php

+
+/*
+ * DO NOT MERGE THIS CHANGE.
+ * Don't load the Webfonts API.
+require __DIR__ . '/experimental/register-webfonts-from-theme-json.php';
 require __DIR__ . '/experimental/class-wp-webfonts.php';
 require __DIR__ . '/experimental/class-wp-webfonts-provider.php';
 require __DIR__ . '/experimental/class-wp-webfonts-provider-local.php';
 require __DIR__ . '/experimental/webfonts.php';
+ */


This is a temporary workaround for testers to test this PR. Once the handler is backported to Core, then (in a separate PR), remove_action( 'plugins_loaded', '_wp_theme_json_webfonts_handler' ); can be added to turn off the stopgate handler in Core and use the Webfonts API.

hellofromtonya · 2022-04-20T23:30:39Z

@peterwilsoncc @desrosj This PR is using the concepts we talked about. What do you think?

@kjellr @jffng I tested it using the TT2 alternative style variations PR. Can you please test it too and share feedback?

peterwilsoncc · 2022-04-21T02:07:03Z

@hellofromtonya I'm getting a fatal error attempting to test this:

Fatal error: Uncaught Error: Call to undefined function gutenberg_add_registered_webfonts_to_theme_json() in /vagrant/content/plugins/gutenberg/lib/experimental/class-wp-theme-json-resolver-gutenberg.php on line 39

My config is:

Twenty Twenty-Two: add alternate style variations wordpress-develop#2440 checked out @ WordPress/wordpress-develop@2a533ca
Gutenberg active with this branch checked out

I tried excluding class-wp-theme-json-resolver-gutenberg.php in the load file but that just caused a different fatal error.

costdev

Currently unable to test due to internet troubles, so in the meantime, here's some suggestions for docblocks, polyfill usage and additional validation.

I'll get testing when I'm back on a stable connection.

lib/experimental/class-theme-json-webfonts-handler.php

peterwilsoncc · 2022-04-21T02:21:04Z

I'm getting a fatal error attempting to test this:

I resolved this by applying this diff, I think it's correct to limit everything to the stopgap only.

diff --git a/lib/experimental/class-wp-theme-json-resolver-gutenberg.php b/lib/experimental/class-wp-theme-json-resolver-gutenberg.php
index 960ea659e8..119489e665 100644
--- a/lib/experimental/class-wp-theme-json-resolver-gutenberg.php
+++ b/lib/experimental/class-wp-theme-json-resolver-gutenberg.php
@@ -36,14 +36,14 @@ class WP_Theme_JSON_Resolver_Gutenberg extends WP_Theme_JSON_Resolver_6_0 {
 		if ( null === static::$theme ) {
 			$theme_json_data = static::read_json_file( static::get_file_path_from_theme( 'theme.json' ) );
 			$theme_json_data = static::translate( $theme_json_data, wp_get_theme()->get( 'TextDomain' ) );
-			$theme_json_data = gutenberg_add_registered_webfonts_to_theme_json( $theme_json_data );
+			// $theme_json_data = gutenberg_add_registered_webfonts_to_theme_json( $theme_json_data );
 			static::$theme   = new WP_Theme_JSON_Gutenberg( $theme_json_data );
 
 			if ( wp_get_theme()->parent() ) {
 				// Get parent theme.json.
 				$parent_theme_json_data = static::read_json_file( static::get_file_path_from_theme( 'theme.json', true ) );
 				$parent_theme_json_data = static::translate( $parent_theme_json_data, wp_get_theme()->parent()->get( 'TextDomain' ) );
-				$parent_theme_json_data = gutenberg_add_registered_webfonts_to_theme_json( $parent_theme_json_data );
+				// $parent_theme_json_data = gutenberg_add_registered_webfonts_to_theme_json( $parent_theme_json_data );
 				$parent_theme           = new WP_Theme_JSON_Gutenberg( $parent_theme_json_data );
 
 				// Merge the child theme.json into the parent theme.json.

costdev · 2022-04-21T04:13:43Z

Tested using the instructions in the PR's description.

Results:

2 @font-face declarations to match what was defined in the theme.json file. ✅
The url should no longer have the file:./ placeholder in it. ✅

Will continue testing.

For others testing by making the manual changes to functions.php and theme.json in TT2, note that you may get a 404 error in console for the font files.

If so, move:

assets/fonts/SourceSerif4Variable-Roman.ttf.woff2 (and other SourceSerif font files)

to

assets/fonts/source-serif-pro/SourceSerif4Variable-Roman.ttf.woff2

lib/experimental/class-theme-json-webfonts-handler.php

peterwilsoncc

I've added a few notes inline.

I tried forcing my way in to using the API from WP CLI (ie, not in theme.json) and wasn't able to find a reasonable way to do so.

Testing with the TT2 branch of WordPress-Develop shows what I'd expect in the source code.

lib/experimental/class-theme-json-webfonts-handler.php

Co-authored-by: Colin Stewart <79332690+costdev@users.noreply.github.com>

hellofromtonya · 2022-04-21T09:13:05Z

In reviewing with @costdev, an enterprising developer who really wants to gain access could use reflection to get access to within the container's class. This means using a class isn't truly non-accessible.

I've switched the design to use anonymous functions (closures) that are stored to variables within the container's scope (as originally suggested by @peterwilsoncc).

hellofromtonya · 2022-04-21T15:14:18Z

@peterwilsoncc Thanks for spotting the fatal error. I had commented those 2 lines out in my testing environment but didn't include them in the PR.

Those 2 lines are now commented out in fb00786.

jffng

👋

I gave this test using TT2's style variations.

The fonts are loading for each variation on the front-end. However in the site editor, only the fonts for the currently saved style variation load:

Kapture.2022-04-21.at.11.12.14.mp4

This issue was at one point fixed here but I'm not sure if that is still relevant to this PR's implementation.

hellofromtonya · 2022-04-21T15:50:46Z

Thanks @jffng for pointing that out. I pushed an update 8295f15 that brings PR #39886 and #40262 into this PR. Can you retest please?

hellofromtonya · 2022-04-21T15:55:48Z

Whoops, sorry I missed the variable name changes. Fixed now in 8295f15.

jffng · 2022-04-21T16:06:10Z

Getting the following fatal:

Fatal error: Uncaught Error: Call to undefined method WP_Theme_JSON_Resolver::get_style_variations() in /Users/jeffreyong/Documents/THEMES/a8c-projects/gutenberg/lib/experimental/class-theme-json-webfonts-handler.php on line 47

hellofromtonya · 2022-04-21T16:17:30Z

Hmm, that new method has been merged into Core (in trunk) WP_Theme_JSON_Resolver::get_style_variations() https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/class-wp-theme-json-resolver.php#L472. I wonder if Gutenberg's Docker image isn't using trunk but instead is using 5.9 release.

I'll add a temporary check to load either Core's version or WP_Theme_JSON_Resolver_6_0 version to accommodate testers who use either testing environment.

hellofromtonya · 2022-04-21T16:28:25Z

Hey @jffng, I switched to use Gutenberg's copy of what's in WP Core trunk 6fb945b. Can you retest please?

costdev · 2022-04-21T16:31:21Z

Getting the following fatal:

Fatal error: Uncaught Error: Call to undefined method WP_Theme_JSON_Resolver::get_style_variations() in /Users/jeffreyong/Documents/THEMES/a8c-projects/gutenberg/lib/experimental/class-theme-json-webfonts-handler.php on line 47

I got the same error and resolved it by changing the call from WP_Theme_JSON_Resolver::get_style_variations() to WP_Theme_JSON_Resolver_6_0::get_style_variations()

Edit: Ah, just saw the commit you linked to Tonya 😛

jffng · 2022-04-21T16:41:18Z

I switched to use Gutenberg's copy of what's in WP Core trunk 6fb945b. Can you retest please?

That did the trick, thank you! All variations and their respective fonts working in the site editor and front-end for me.

bph · 2022-04-21T17:59:34Z

Tested it with TT2 and modifications according to above instructions today's modifications.

Font face as expected in the header / front end

Font face as expected in the header / front end

Font Family in dropdown for Typography was available (Styles, Site Title block)

costdev · 2022-04-22T11:09:32Z

I've been testing with the design change to use anonymous functions as variables within the container. This appears to fully prevent direct interaction with the API. In other words, I can't find a way to use the API in a backwards-incompatible way.

LGTM 👍

ndiego · 2022-04-25T10:15:09Z

Hi all, do we have an ETA on when this will be merged?

hellofromtonya · 2022-04-25T11:11:25Z

Hi all, do we have an ETA on when this will be merged?

@ndiego before Beta 3's (April 26th) release party. Here's the backport PR in WP Core WordPress/wordpress-develop#2622.

Adds `_wp_theme_json_webfonts_handler()` for handling `fontFace` declarations in a theme's `theme.json` file to generate the `@font-face` styles for both the editor and front-end. Design notes: * It is not a public API, but rather an internal, Core-only handler. * It is a stopgap implementation that will be replaced when the public Webfonts API is introduced in Core. * The code design is intentional, albeit funky, with the purpose of avoiding backwards-compatibility issues when the public Webfonts API is introduced in Core. * It hides the inter-workings. * Does not exposing API ins and outs for external consumption. * Only works for `theme.json`. * Does not provide registration or enqueuing access for plugins. For more context on the decision to include this stopgap and the Webfonts API, see: * Core's PR 40493 WordPress/gutenberg#40493 * Gutenberg's tracking issue 40472 WordPress/gutenberg#40472 Props aristath, hellofromTonya, peterwilsoncc, costdev, jffng, zieladam, gziolo, bph, jonoaldersonwp, desrosj. See #55567, #46370. git-svn-id: https://develop.svn.wordpress.org/trunk@53282 602fd350-edb4-49c9-b593-d223f7449a82

Adds `_wp_theme_json_webfonts_handler()` for handling `fontFace` declarations in a theme's `theme.json` file to generate the `@font-face` styles for both the editor and front-end. Design notes: * It is not a public API, but rather an internal, Core-only handler. * It is a stopgap implementation that will be replaced when the public Webfonts API is introduced in Core. * The code design is intentional, albeit funky, with the purpose of avoiding backwards-compatibility issues when the public Webfonts API is introduced in Core. * It hides the inter-workings. * Does not exposing API ins and outs for external consumption. * Only works for `theme.json`. * Does not provide registration or enqueuing access for plugins. For more context on the decision to include this stopgap and the Webfonts API, see: * Core's PR 40493 WordPress/gutenberg#40493 * Gutenberg's tracking issue 40472 WordPress/gutenberg#40472 Props aristath, hellofromTonya, peterwilsoncc, costdev, jffng, zieladam, gziolo, bph, jonoaldersonwp, desrosj. See #55567, #46370. Built from https://develop.svn.wordpress.org/trunk@53282 git-svn-id: http://core.svn.wordpress.org/trunk@52871 1a063a9b-81f0-0310-95a4-ce76da25c4cd

Adds `_wp_theme_json_webfonts_handler()` for handling `fontFace` declarations in a theme's `theme.json` file to generate the `@font-face` styles for both the editor and front-end. Design notes: * It is not a public API, but rather an internal, Core-only handler. * It is a stopgap implementation that will be replaced when the public Webfonts API is introduced in Core. * The code design is intentional, albeit funky, with the purpose of avoiding backwards-compatibility issues when the public Webfonts API is introduced in Core. * It hides the inter-workings. * Does not exposing API ins and outs for external consumption. * Only works for `theme.json`. * Does not provide registration or enqueuing access for plugins. For more context on the decision to include this stopgap and the Webfonts API, see: * Core's PR 40493 WordPress/gutenberg#40493 * Gutenberg's tracking issue 40472 WordPress/gutenberg#40472 Props aristath, hellofromTonya, peterwilsoncc, costdev, jffng, zieladam, gziolo, bph, jonoaldersonwp, desrosj. See #55567, #46370. Built from https://develop.svn.wordpress.org/trunk@53282 git-svn-id: https://core.svn.wordpress.org/trunk@52871 1a063a9b-81f0-0310-95a4-ce76da25c4cd

hellofromtonya · 2022-04-26T14:51:16Z

Closing this PR. Why?

It's been backported to WordPress Core for 6.0 Beta 3 via https://core.trac.wordpress.org/changeset/53282.
Does not need to exist in Gutenberg.

Thank you everyone for contributing!

oandregal · 2022-04-27T13:59:27Z

lib/compat/wordpress-6.0/theme-json-webfonts-handler.php

+			}
+
+			// Bail out early if there are no settings for webfonts.
+			if ( empty( $settings['typography'] ) || empty( $settings['typography']['fontFamilies'] ) ) {


Font families can be defined at the top-level, as in:

{ "settings": { "typography": { "fontFamilies": [] } } }

But also can be defined per block, as in:

{ "settings": { "typography": { "fontFamilies": [] // Fonts for all. }, "blocks": { "some/block": { "typography": { "fontFamilies": [] // A block can define its own. } } } } }

Is this problematic for webfonts? How can a webfont be defined for a single block?

Is this problematic for webfonts? How can a webfont be defined for a single block?

@oandregal Top-level only in this first version.

I remember a discussion thread (not sure where it happened) where @mtias indicated not having block-level web font selection. Also see #40362.

hellofromtonya added the [Feature] Webfonts label Apr 20, 2022

hellofromtonya self-assigned this Apr 20, 2022

hellofromtonya linked an issue Apr 20, 2022 that may be closed by this pull request

Move webfonts handling to internal only (not accessible) - WP 6.0 Stopgap #40472

Closed

7 tasks

hellofromtonya requested review from peterwilsoncc, gziolo, adamziel and desrosj April 20, 2022 22:49

Adds stopgap handler for theme.json webfonts.

f109cb7

hellofromtonya force-pushed the try/stopgap-themejson-webfonts branch from c6d5bd7 to f109cb7 Compare April 20, 2022 23:14

hellofromtonya marked this pull request as ready for review April 20, 2022 23:14

hellofromtonya requested review from TimothyBJacobs and spacedmonkey as code owners April 20, 2022 23:14

hellofromtonya commented Apr 20, 2022

View reviewed changes

hellofromtonya mentioned this pull request Apr 20, 2022

Move webfonts handling to internal only (not accessible) - WP 6.0 Stopgap #40472

Closed

7 tasks

hellofromtonya requested review from jffng and kjellr April 20, 2022 23:29

costdev requested changes Apr 21, 2022

View reviewed changes

costdev reviewed Apr 21, 2022

View reviewed changes

lib/experimental/class-theme-json-webfonts-handler.php Outdated Show resolved Hide resolved

peterwilsoncc reviewed Apr 21, 2022

View reviewed changes

lib/experimental/class-theme-json-webfonts-handler.php Outdated Show resolved Hide resolved

lib/experimental/class-theme-json-webfonts-handler.php Outdated Show resolved Hide resolved

lib/experimental/class-theme-json-webfonts-handler.php Outdated Show resolved Hide resolved

Tonya Mork and others added 5 commits April 21, 2022 03:33

Updates DocBlock from code review.

eca6343

Co-authored-by: Colin Stewart <79332690+costdev@users.noreply.github.com>

Use str_starts_with() instead of strpos().

45c2c88

Co-authored-by: Colin Stewart <79332690+costdev@users.noreply.github.com>

Fix guarding conditions.

99a14e9

Sanitize src URLs.

4f6f098

Remove wp_print_footer_scripts hook.

e32700d

Adds home_url() as a relative link check.

66926e2

jffng reviewed Apr 21, 2022

View reviewed changes

Add webfonts defined in variations when in the editor.

8295f15

hellofromtonya force-pushed the try/stopgap-themejson-webfonts branch from 87c5ca6 to 8295f15 Compare April 21, 2022 15:54

Use WP_Theme_JSON_Resolver_6_0 instead of latest in WP Core trunk.

6fb945b

hellofromtonya added 2 commits April 22, 2022 03:47

Rename file, no longer a class.

66d182a

Relocate file for backport.

5047488

hellofromtonya added the Backport to WP 6.7 Beta/RC Pull request that needs to be backported to the WordPress major release that's currently in beta label Apr 22, 2022

Remove reassignment of $settings array level init (micro-optimization).

743ca6d

costdev approved these changes Apr 22, 2022

View reviewed changes

hellofromtonya mentioned this pull request Apr 22, 2022

Backport: theme.json webfonts handler - WP 6.0 stopgap WordPress/wordpress-develop#2622

Closed

hellofromtonya closed this Apr 26, 2022

hellofromtonya removed the Backport to WP 6.7 Beta/RC Pull request that needs to be backported to the WordPress major release that's currently in beta label Apr 26, 2022

oandregal reviewed Apr 27, 2022

View reviewed changes

hellofromtonya deleted the try/stopgap-themejson-webfonts branch August 9, 2022 21:36

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Webfonts: Add internal-only theme.json webfonts handler - WP 6.0 stopgap #40493

Webfonts: Add internal-only theme.json webfonts handler - WP 6.0 stopgap #40493

hellofromtonya commented Apr 20, 2022 •

edited

Loading

hellofromtonya Apr 20, 2022

hellofromtonya commented Apr 20, 2022

peterwilsoncc commented Apr 21, 2022

costdev left a comment

peterwilsoncc commented Apr 21, 2022

costdev commented Apr 21, 2022

peterwilsoncc left a comment

hellofromtonya commented Apr 21, 2022 •

edited

Loading

hellofromtonya commented Apr 21, 2022

jffng left a comment

hellofromtonya commented Apr 21, 2022 •

edited

Loading

hellofromtonya commented Apr 21, 2022

jffng commented Apr 21, 2022

hellofromtonya commented Apr 21, 2022

hellofromtonya commented Apr 21, 2022

costdev commented Apr 21, 2022 •

edited

Loading

jffng commented Apr 21, 2022

bph commented Apr 21, 2022 •

edited

Loading

costdev commented Apr 22, 2022

ndiego commented Apr 25, 2022

hellofromtonya commented Apr 25, 2022

hellofromtonya commented Apr 26, 2022

oandregal Apr 27, 2022 •

edited

Loading

hellofromtonya Apr 27, 2022

Webfonts: Add internal-only theme.json webfonts handler - WP 6.0 stopgap #40493

Webfonts: Add internal-only theme.json webfonts handler - WP 6.0 stopgap #40493

Conversation

hellofromtonya commented Apr 20, 2022 • edited Loading

What?

Why?

How?

Testing Instructions

Set up instructions:

How to Test

How to Test on the front-end

How to Test in the back-end

Design Considerations

hellofromtonya Apr 20, 2022

Choose a reason for hiding this comment

hellofromtonya commented Apr 20, 2022

peterwilsoncc commented Apr 21, 2022

costdev left a comment

Choose a reason for hiding this comment

peterwilsoncc commented Apr 21, 2022

costdev commented Apr 21, 2022

peterwilsoncc left a comment

Choose a reason for hiding this comment

hellofromtonya commented Apr 21, 2022 • edited Loading

hellofromtonya commented Apr 21, 2022

jffng left a comment

Choose a reason for hiding this comment

hellofromtonya commented Apr 21, 2022 • edited Loading

hellofromtonya commented Apr 21, 2022

jffng commented Apr 21, 2022

hellofromtonya commented Apr 21, 2022

hellofromtonya commented Apr 21, 2022

costdev commented Apr 21, 2022 • edited Loading

jffng commented Apr 21, 2022

bph commented Apr 21, 2022 • edited Loading

costdev commented Apr 22, 2022

ndiego commented Apr 25, 2022

hellofromtonya commented Apr 25, 2022

hellofromtonya commented Apr 26, 2022

oandregal Apr 27, 2022 • edited Loading

Choose a reason for hiding this comment

hellofromtonya Apr 27, 2022

Choose a reason for hiding this comment

hellofromtonya commented Apr 20, 2022 •

edited

Loading

hellofromtonya commented Apr 21, 2022 •

edited

Loading

hellofromtonya commented Apr 21, 2022 •

edited

Loading

costdev commented Apr 21, 2022 •

edited

Loading

bph commented Apr 21, 2022 •

edited

Loading

oandregal Apr 27, 2022 •

edited

Loading