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
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
Issue is how IE/EDGE handles truncation of inline-block items - it seems to treat them as a single character, so truncates the entire inline-block down to an ellipsis. If display: inline is used here, all's well. Firefox does similar - seems that Chrome is the outlier here.
More context:-
we use display: inline-block on because the browser will ignore line-height on inline elements if the nearest block-level ancestor has a larger line-height.
we also need display: inline-block on when we ellipse text with "maxWidth", it doesn't work on an inline element.
additionally, we use vertical-align: baseline to line up the baseline of text characters regardless of font-size, line-height, etc. BUT the browser says "nope" and forces vertical-align: bottom when overflow:hidden is added for maxWidth-ellipsed text. this throws off our vertical rhythm between different text on the same line, so we have rem vertical-align adjustments for these cases.
but i've found that these are not reliable across browsers, Safari will adjust adjacent text higher or lower so i'm sure IE/Edge also has some wonkiness.
long story short, we might want to rethink , possibly doing the following:
set to display: inline
remove the maxWidth option from , find a different way to ellipse complicated groups of inline text (like in our message byline)
just have to know that sized will match the vertical-align of its closest ancestor with a specified "textSize".
The text was updated successfully, but these errors were encountered:
Issue is how IE/EDGE handles truncation of inline-block items - it seems to treat them as a single character, so truncates the entire inline-block down to an ellipsis. If display: inline is used here, all's well. Firefox does similar - seems that Chrome is the outlier here.
More context:-
long story short, we might want to rethink , possibly doing the following:
The text was updated successfully, but these errors were encountered: