Benoît Rouleau

If anyone's interested, here is the bug on WebKit: https://bugs.webkit.org/show_bug.cgi?id=137730 It doesn't seem to be getting a lot of attention, even though it's a pretty serious issue for some layouts......

The `font-variant-*` properties seem more suited with Tailwind's utility approach than the `font-feature-settings` property, because that would break as soon as you want to change more than one feature on...

@martinfjant I'm planning on adding support for caps, numeric, and ligatures as above. Do you have any feedback on the class names? As for the other features, `font-variant-position` and `font-variant-alternates`...

Thank you @martinfjant, I just released [`v2.2.0`](https://github.com/benface/tailwindcss-typography/releases/tag/v2.2.0) with utilities for caps, nums, and ligatures. I will keep this issue open to discuss other OpenType features to implement in the future,...

@felipepodesta Which OpenType feature(s) are you missing? Any suggestions on how to implement them (class names)?

Heads up: the classes for caps, nums, and ligatures will change in v3.0 of the plugin, because I'm adding them to the `theme` to allow customizing them (instead of just...

Interesting idea @jonathan-s. Do you have any idea for what the API could be like?

I'm hesitant to add this because the spec in which the `hanging-punctuation` property is defined (CSS Text Module Level 3) is still a Working Draft, which probably explains why only...

@gangsthub Sorry I guess I wasn’t clear. I know this already, but I would like a way to store all paths except a few that I specify. That way when...

Yes, sure could. Thanks for sharing that code. Feel free to close this if you think it’s not worth adding as an official API.