Skip to content

Updating how the font loaded via data-uri is called - #2

Open
moliver-hemasystems wants to merge 1 commit into
RoelN:masterfrom
moliver-hemasystems:update_data_uri_for_ttf
Open

moliver-hemasystems wants to merge 1 commit into
RoelN:masterfrom
moliver-hemasystems:update_data_uri_for_ttf

Conversation

@moliver-hemasystems

@moliver-hemasystems moliver-hemasystems commented Oct 26, 2021

Copy link
Copy Markdown

Recently, on some OSes (like MacOS Monterey), the check using the truetype font via data-uri started throwing the following error (provided by Firefox v93.0):

downloadable font: not usable by platform (font-family: "pixelambacht" style:normal weight:400 stretch:100 src index:0) source: data:font/truetype;base64,AAEAAAALAIAAAwAwT1MvMghABuMAAAC8AAAAYGNtYXAAlQDaAAABHAAAAGRnYXNw//8ABAAAAYAAAAAIZ2x5Zv8nt3kAAAGIAAAATG … AQQJAAQAAgAOAAMAAQQJAAUAAAAAAAMAAQQJAAYAAAAAAAMAAQQJAAoAAAAAAAD+/wBy/v8Ab/7/AGX+/wBsAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

This was resulting in the check failing when it should have been passing.

Updating how the data-uri was set to include things like format() seemed to resolve the errors, but Firefox was still warning:

downloadable font: no supported format found (font-family: "pixelambacht" style:normal weight:400 stretch:100 src index:1) source: (end of source list)

... and the check was still failing when it should have been passing.

Changing to use the WOFF font instead of the TrueType font resolved the warning, and allowed the check to work properly again.

Recently, on some OSes (like MacOS Monterey), the check using the truetype font via data-uri started throwing the following error (provided by Firefox v93.0):

```
downloadable font: not usable by platform (font-family: "pixelambacht" style:normal weight:400 stretch:100 src index:0) source: data:font/truetype;base64,AAEAAAALAIAAAwAwT1MvMghABuMAAAC8AAAAYGNtYXAAlQDaAAABHAAAAGRnYXNw//8ABAAAAYAAAAAIZ2x5Zv8nt3kAAAGIAAAATG … AQQJAAQAAgAOAAMAAQQJAAUAAAAAAAMAAQQJAAYAAAAAAAMAAQQJAAoAAAAAAAD+/wBy/v8Ab/7/AGX+/wBsAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
```

Updating how the data-uri was set to include things like `format()` seemed to resolve the errors, but Firefox was still warning:

```
downloadable font: no supported format found (font-family: "pixelambacht" style:normal weight:400 stretch:100 src index:1) source: (end of source list)
```

... and the check was still failing when it should have been passing.

Changing to use the WOFF font instead of the TrueType font resolved the warning, and allowed the check to work properly again.
@moliver-hemasystems

Copy link
Copy Markdown
Author

I wanted to also point out that the previous version was also getting a warning from Firefox about:

downloadable font: OS/2: Bad sTypoLineGap, setting it to 0: -32 (font-family: "pixelambacht" style:normal weight:400 stretch:100 src index:0) source: data:font/truetype;base64,AAEAAAALAIAAAwAwT1MvMghABuMAAAC8AAAAYGNtYXAAlQDaAAABHAAAAGRnYXNw//8ABAAAAYAAAAAIZ2x5Zv8nt3kAAAGIAAAATG … AQQJAAQAAgAOAAMAAQQJAAUAAAAAAAMAAQQJAAYAAAAAAAMAAQQJAAoAAAAAAAD+/wBy/v8Ab/7/AGX+/wBsAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

However, the version in the PR also results in this warning, just with the updated source. It doesn't seem to affect anything as far as I can tell.

@moliver-hemasystems

Copy link
Copy Markdown
Author

Also, according to caniuse.com, woff seems to have better browser support now than ttf, so this should hopefully be an acceptable change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant