Just tried playing the game, and found my very first actual breakage due to blocking custom fonts in over five years of using the web like this.
It just puts up a “NetworkError: A network error occurred.” error and doesn’t start.
The reason is this:
await document.fonts.load(`14px ${font_family}`)
Since this isn’t actually necessary for page functionality, it would be better wrapped in a try { … } catch {}, or just with .catch(() => {}) appended.
My bizarre workaround is a user stylesheet to remove the offending font:
:root {
--glkote-mono-family: monospace;
}
Honestly, I’m a little surprised it took five years to find something that actually broke completely from this.
It might be worth clarifying that the game itself does not deal in typefaces: it's the interpreter running the game that handles font business. The link in the article leads to the web-based Parchment interpreter running on iplayif.com, but there are other alternatives both for web-based play and native applications.
Maybe the Parchment people would appreciate the bug report, though. Or if it's iplayif.com that introduces this bug. I have no idea!
It just puts up a “NetworkError: A network error occurred.” error and doesn’t start.
The reason is this:
Since this isn’t actually necessary for page functionality, it would be better wrapped in a try { … } catch {}, or just with .catch(() => {}) appended.My bizarre workaround is a user stylesheet to remove the offending font:
Honestly, I’m a little surprised it took five years to find something that actually broke completely from this.