Update: Apparently it works fine now even with the child theme sub-directory. I have no clue what would have caused that. But I just now tested again with the directory nested in the child theme and it seems to read from it fine, when yesterday it wasn’t resolving at all. Do you have experience with servers possibly causing this issue? I’m running an Apache VPS at the moment.
________
Hi David! In response to post #943403, I did a bit more testing. I usually use Typekit syncing for hosted fonts or other platforms so I’m a bit confused what might be causing the issue of Chrome not resolving fonts if they aren’t located in the /uploads/2019/XX directory.