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

Fix AddProjectMemberDialog, remove scroll artifacts #10785

Merged
merged 1 commit into from
Apr 17, 2024

Conversation

torchiaf
Copy link
Contributor

@torchiaf torchiaf commented Apr 11, 2024

Summary

Fixes #10784

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

Checklist

  • The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
  • The PR has a Milestone
  • The PR template has been filled out
  • The PR has been self reviewed
  • The PR has a reviewer assigned
  • The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
  • The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

@torchiaf torchiaf added this to the v2.9.0 milestone Apr 11, 2024
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to change pkg/rancher-components/src/components/Card/Card.vue instead of AddProjectMemberDialog?

Copy link
Contributor Author

@torchiaf torchiaf Apr 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, but I was wondering if it can introduce side effects in other components where we are using Card.vue; however, I went through the UI and couldn't find any regressions.

@@ -177,4 +177,7 @@ export default {
border: 1px solid var(--border);
box-shadow: none;
}
.card-container.card-sticky .card-wrap .card-body {
overflow: hidden
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would auto be more appropriate than hidden? I don't want to end up with a scenario where we would require scrolling, but are unable to do so.

Signed-off-by: Francesco Torchia <francesco.torchia@suse.com>
Copy link
Member

@rak-phillip rak-phillip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@torchiaf torchiaf merged commit 8ee0f7f into rancher:master Apr 17, 2024
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Modals: scroll artifact bugs
2 participants