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

Internally linked task cards with long titles have incorrectly wrapping text #5401

Open
4 tasks done
nekohayo opened this issue Jan 14, 2024 · 1 comment
Open
4 tasks done

Comments

@nekohayo
Copy link
Contributor

nekohayo commented Jan 14, 2024

Checklist

  • I verified that Kanboard is correctly installed
  • I verified that the problem does not come from a plugin
  • I verified that the problem is not already reported
  • I understand that Kanboard is in maintenance mode. It doesn't mean it's abandoned, but there is no significant feature development

Actual behaviour

When a row item is too long in the "Internal links" section of a task's details, it will wrap the text completely to the left of the row, without taking the "⚙️⏷" into account.

In comparison, this does not affect the "Subtasks" table, which correctly wraps the text after the "⤭⚙️⏷☐" section.

Expected behaviour

Line wrapping should be aligned to be after the "⚙️⏷"; in other words, it should behave like the nice "Subtasks" table's behavior.

I haven't tested the "External links" or "Attachments" features, but presumably they might be affected by the same problem too?

Steps to reproduce

Create a task card that has internal links to other task cards that have long titles, and watch the line wrap below its gear icon.

Screenshots

Circled in red is the incorrect behavior, circled in green is the expected behavior:

image

Configuration

  • Kanboard version: 1.2.33 and 1.2.34
  • Database type and version: SQLite 3.40.1
  • PHP version: 8.2.14
  • OS: Fedora 39
  • Browser: Firefox 121
@nekohayo nekohayo added the bug label Jan 14, 2024
@nekohayo
Copy link
Contributor Author

For reference, the reason why the "Subtasks" table is not affected by this issue is that it was fixed in PR #4366 by @identei as part of issue #4213.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants