Daniel Howe

Thanks for this @SableRaf I'm not seeing the behavior you describe in processing, at least in 4.3:  I also don't see it in...

Understood. I'm wondering if this is a duplicate of https://github.com/processing/p5.js/issues/4652, which was marked as completed (but may not be). Is this only an issue when a single 'word' is wider...

My 2-centz is to opt for backwards-compatibility... Whatever the ideal solution (I don't remember why we did this the first time around), there are lots of 1.x sketches out there...

The issue here is that we get glyph data for some fonts and not others. Loading them via FontFace is a fallback that allows the font to render in 2D,...

> [@dhowe](https://github.com/dhowe) do you think [the original sketch](https://editor.p5js.org/davepagurek/sketches/c8__rjh8_) in the issue has the same issue? It's all in the 2D renderer so FontFace should be sufficient. Maybe something again with...

> Oh interesting, maybe it's a Firefox specific issue? I get this: confirmed here as well - spaces cause this error in FF, fixed in #7555

@aferriss this should be fixed in #7555

So yes, there is more to parsing a woff2 than simply decompressing. I'm also not sure if they need to parsed completely or if they can be converted easily to...

Hi all. So these are actually two different functions, with different intended behavior. The latter operates on a custom/loaded font _only_, and returns the exact bounds for a specific string...

v2.0 will provide `textBounds()` and `textWidth()` for tight (string-specific) bounds, and `fontBounds()` and `fontWidth()` for loose (font-specific) bounds, for all fonts - hopefully this should resolve any lack of clarity...