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
I'm so excited this is finally out 🎉
However, since it's still experimental on newer browser versions, we should probably wrap it (pun intended) in the CSS @supports rule to be on the safer side if we're looking to implement it?
Hmm, good suggestion @reemhamz, but I’m not 100% sure we’d need that in this case. @supports is useful for when we want to fallback to a different rule in older browsers, but I’m not sure if there’s an existing text-wrap value we’d need to fall back to here? If an older browser encounters a CSS rule it does not yet understand, it should just safely ignore it.
The CSS property
text-wrap: balance;
is now supported in Firefox 121, and has pretty good support across browsers: https://developer.mozilla.org/en-US/docs/Web/CSS/text-wrapI propose we should add this to all heading elements in Protocol's base styles as a general typographical improvement.
The text was updated successfully, but these errors were encountered: