-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Pagination button for basic table shows text that is cut off at the bottom #1486
Comments
@FriedhelmWS I found the original request that introduced the change #1342, it seems it fixed another styling issue, changing it to |
@ruanyl Yes, I noticed the original I think if we do so, the original behavior of the button baseline alignment (which is intended) would not be affected, but can also fix the issue of the button text. This do require some more checking for regression though. |
@FriedhelmWS Adding <div style={{lineHeight: 100}}>
<OuiButtonEmpty />
</div> This button will have line height I think we should remove |
Removed `line-height: inherit` introduced by opensearch-project#1342 and use `display: flex` to fix the original issue. With this commit, it also fixed the issue described in opensearch-project#1486 Signed-off-by: Yulong Ruan <[email protected]>
Describe the bug
A few pixels appear to be cut off from the bottom of the pagination button (empty button), as shown in the screenshots. This issue doesn't appear to occur with empty buttons that are used alone.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No cut off
Screenshots
In OSD:
In OUI documentation (not very obvious due to background):
Host/Environment:
Additional context
Causes
In
_button_empty.scss
:The
line-height: inherit;
property causes the button text to inherit aline-height: 1;
from ouiBody, which doesn't provide enough height to fully display characters with descenders, such as 'g' and 'y'.Suggested Fix
Add
line-height: normal;
to the button text only so that the line height is auto-adjusted by the browser (roughly 1.2 according to the docs), without changing the inherited behavior of the parent button styles.The text was updated successfully, but these errors were encountered: