Ok. I jumped the gun a wee bit. It looks like a definite bug.
After checking the website on other machines Win10, Mac & iOS, yet untried, on multiple browsers, the font loading fault still appears. Still reporting as a fault in developer tools (Chrome) 404 error.
So this is what’s I think is happening.
If public_html/g/fonts.css exists then when you edit then publish in Sitejet Builder no fonts folder nest will be created and if the fonts folder nest exists it will be deleted. So font.css must not exist for a successful upload via Sitejet to occur.
Therefore if you’ve viewed the website successfully previously after a successful upload those font files are cached by the browser. Therefore this error goes unnoticed after subsequent edits. At least until the cache is cleared.
Anyone else viewing on another machine WILL get the error, 404 as fonts being looked for do not exist on server (as viewed in cpanel).
Deleting fonts.css (or renaming fonts.css to fonts.csx, for example) BEFORE publishing vie Sitejet Builder forces both a new fonts.css files AND a new nest of folders containing the fonts to be written.
After that all is good.
It’s worth checking, via cpanel file manager, for public_html/g/fonts… after publishing to check this has worked. Don’t forget to refresh the page first. If fonts.cssis the only thing there then delete it and try publishing the site again.
Hopefully a dev will check it out and find a fix because with those font files being cached by the browser it’s an easy error to miss after an edit and re-publish vie Sitejet Builder.
Andy