You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off: Love what you're doing and providing with this plugin! Works like a charm!
On to my question:
How does fluid-tailwind manage support for "non-clamp-browsers"? Is there a way I can implement it with fallbacks?
Now, it looks like the font size for example just becomes the base size when clamp isn't supported.
When I add the regular "text-" tailwind classes to set a fallback, they override the fluid ones. Also, intellisense doesn't like to see the same utility twice.
This question might have already been asked before, but I couldn't find an answer, so thought I'd ask here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
First off: Love what you're doing and providing with this plugin! Works like a charm!
On to my question:
How does fluid-tailwind manage support for "non-clamp-browsers"? Is there a way I can implement it with fallbacks?
Now, it looks like the font size for example just becomes the base size when clamp isn't supported.
When I add the regular "text-" tailwind classes to set a fallback, they override the fluid ones. Also, intellisense doesn't like to see the same utility twice.
This question might have already been asked before, but I couldn't find an answer, so thought I'd ask here.
Thanks in advance!
Raf
Beta Was this translation helpful? Give feedback.
All reactions