Skip to content
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

[Analytical Table]: [Top padding of cell is reduced during PopIn] #5977

Closed
1 task done
dhruvojha opened this issue Jun 26, 2024 · 1 comment · Fixed by #6170
Closed
1 task done

[Analytical Table]: [Top padding of cell is reduced during PopIn] #5977

dhruvojha opened this issue Jun 26, 2024 · 1 comment · Fixed by #6170
Labels
bug Something isn't working released

Comments

@dhruvojha
Copy link

dhruvojha commented Jun 26, 2024

Describe the bug

When a particular table is popped in, the top padding for the data in the cell for the first column is much reduced.

Isolated Example

No response

Reproduction steps

  1. Go to the Analytical table documentation in storybook.
  2. Go to the popIn example.
  3. Adjust the scale from auto to 600. you will see change in padding between Name column header and data entry 'Allen Best'
    ...

Expected Behaviour

The padding should remain the same, as per guidelines from SAP UX team.

Screenshots or Videos

Screenshot 2024-06-26 at 2 10 47 PM Screenshot 2024-06-25 at 4 03 58 PM

UI5 Web Components for React Version

v1.29.2

UI5 Web Components Version

v1.24.5

Browser

Chrome

Operating System

MacOS

Additional Context

No response

Relevant log output

No response

Organization

No response

Declaration

  • I’m not disclosing any internal or sensitive information.
@ui5-webcomponents-react-bot
Copy link
Contributor

🎉 This issue has been resolved in version v2.0.0-rc.2 🎉

The release is available on v2.0.0-rc.2

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released
Projects
Status: 🆕 New
Development

Successfully merging a pull request may close this issue.

2 participants