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

Inline Field data overflowing on Kanban cards #6000

Closed
Bonapara opened this issue Jun 24, 2024 · 8 comments
Closed

Inline Field data overflowing on Kanban cards #6000

Bonapara opened this issue Jun 24, 2024 · 8 comments
Assignees
Labels
good first issue Good for newcomers scope: front Issues that are affecting the frontend side only

Comments

@Bonapara
Copy link
Member

Current Behavior

The inline field data overflows on Kanban cards.

image

Desired Behavior

The content should be cropped with ellipses to prevent overflow.

@Bonapara Bonapara added good first issue Good for newcomers scope: front Issues that are affecting the frontend side only size: minutes labels Jun 24, 2024
Copy link
Contributor

greptile-apps bot commented Jun 24, 2024

To fix the overflow issue on Kanban cards, update the CSS in the RecordBoardCard and RecordShowContainer components. Add the following styles to the relevant elements:

.element-selector {
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}

Replace .element-selector with the actual class or element selector used for the inline field data in these components.

References

@rksingh2001
Copy link
Contributor

Can I get assigned to this issue?

@Bonapara
Copy link
Member Author

Sure @rksingh2001, thanks for contributing!

@rksingh2001
Copy link
Contributor

rksingh2001 commented Jun 25, 2024

Hi @Bonapara, I have implemented ellipses for the straightforward text like field types, what about multi select types. I don't think ellipsis will work for them.
image

@Bonapara
Copy link
Member Author

Thanks @rksingh2001! Yes, it should be the case for every field. But the Link and Multi-Select field have special behavior: #4900

@lucasbordeau
Copy link
Contributor

Closing this issue as it has been fixed by recent changes.

@rksingh2001
Copy link
Contributor

@lucasbordeau, I would like to learn how it was fixed, can you point me to PR which fixed it or change (if u remember)? I will appreciate it.

@lucasbordeau
Copy link
Contributor

@rksingh2001 This issue was fixed by #6061

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers scope: front Issues that are affecting the frontend side only
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants