deck
deck copied to clipboard
nextcloud
Wrap card title when editing
Describe the bug This is and UI issue. When I click on a card, the details view appear on the right. When the title of the card is long, the text is wrapped with line breaks. If I click on the title to edit the text, the wrapping disappears and the text field is only a single line. This is very distracting as (1) the layout unexpectedly change and (2) editing a long text in a single line text field is a pain.
To Reproduce Steps to reproduce the behavior:
- Create a new card with a long title.
- Click on the card.
- Look at the details view on the right.
- Click on the title in the details view.
Expected behavior Keep the wrapping of the text.
Screenshots
Before I have clicked on the title.
After I have clicked on the title.
Additional details from the discussions
- This should also be the case for the card view
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Yes, we probably should just use a contenteditable element, so we have proper support for multiple lines.
We currently don't have editing capabilities in the sidebar in the vue rewrite, needs to be done before the release.
@juliushaertl I see you closed the bug about wrapping title in cards (https://github.com/nextcloud/deck/issues/1572) view as a duplicate of this one. Personally, I would prefer to track wrapping in cards view vs in detail view in two different issues, because it will also be separate pull requests. But you seem to be involved in development here, so do it how you like it better.
But then can you change the title of this issue to "wrap title in card view and details view during editing"?
@juliushaertl you modified the milestone various times, now it was removed. Was that intentional / is this issue lower priority now?
Just to understand.
As far as I can see, a lot of duplicates/related issues were closed, and this is the issue that tracks title wrapping in both the card and sidebar view.
Not really a lower priority, but just not scheduled yet since it didn't make it into 1.2 and 1.3. We'll need to see if we can make time for it in one of the upcoming release plannings.