jfkthame
jfkthame
> Do we know of any implementations (besides OTS) that isn't happy with the tuples we emit? I don't know offhand. But I'm instinctively cautious about going outside a limit...
Thanks for the comment, Ian, that's interesting. I'm curious if people considered the implications of this for dynamically-varying line-clamp, or looked only at static examples? In the purely static case,...
To my mind, the `waterfall` name would only be appropriate if used in the vertical axis. For the horizontal version (e.g. like I see in Google [image search results](www.google.com/search?q=waterfall&tbm=isch)), `masonry`...
ISTM that explicitly saying a collection without a fragment ID (font name) is ignored as invalid would be just as straightforward, and more consistent with the general rejection of indexing...
I've definitely seen fonts with incorrect bounding-box data, though I don't recall the specific examples, and this did result in clipped rendering in some context (which is what led to...
> "for a given well-defined font and text input, across browser implementations, the maximum possible extent of ink overflow from hanging glyphs is no more that a 2px outset from...
> From [Use CSS to boost the font size of emoji with no extra markup](https://shkspr.mobi/blog/2024/04/use-css-to-boost-the-font-size-of-emoji-with-no-extra-markup/) by Terence Eden @edent > > > Emoji codepoints are complicated - especially when it...
> Thanks for doing that. Non owner LGTM, but I am wondering if when option `colr-cycle-check` is set to false the whole traversal could be skipped? It's probably still desirable...
> I would find that case unlikely and likely not worth the extra traversal overhead for every glyph. Agree, it's unlikely that a page author would inadvertently deploy a font...