[p5.js 2.0 Beta Bug Report]: Some google fonts don't load
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24k
- Forks
- 3.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 25
Description
Most appropriate sub-area of p5.js?
- Accessibility
- Color
- Core/Environment/Rendering
- Data
- DOM
- Events
- Image
- IO
- Math
- Typography
- Utilities
- WebGL
- Build process
- Unit testing
- Internationalization
- Friendly errors
- Other (specify if possible)
p5.js version
2.0 beta 1
Web browser and version
Firefox
Operating system
MacOS
Steps to reproduce this
I'm not sure what the difference is, but I was playing around with loading google fonts, and I have an example of one that works and one that doesn't:
let font
async function setup() {
createCanvas(400, 400);
// ok
// font = await loadFont('https://fonts.googleapis.com/css2?family=Sniglet:wght@400;800&display=swap')
// not ok?
font = await loadFont('https://fonts.googleapis.com/css2?family=Jersey+10&display=swap')
}
function draw() {
background(220);
textFont(font)
textSize(20)
text('test', 50, 50)
}
Live: https://editor.p5js.org/davepagurek/sketches/c8__rjh8_
Anyone have any ideas what Jersey 10 does that Sniglet doesn't that would the error Failed to create FontFace for "Jersey 10" to be thrown? Maybe the number in the name?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the linked sketch in Firefox and comparing the loadFont() behavior for the Sniglet and Jersey 10 Google Fonts URLs. Investigate why Jersey 10 triggers “Failed to create FontFace” and consider the existing font-loading path; done when the reported font loads successfully without breaking the working case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100