nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

While creating a title for a card, the viewable box shrunk to 1.5-2 lines and will not expand.

Bonnie Bright

I was creating many cards with now issue. Then, while filling out the title, the spacing no longer expanded as I typed and it's not fixed at 1.5-2 lines. I say 1.5-2 line because, if I type just past one line worth of text, the second line is only half visible. If I type a full two lines worth of text, then two lines are visible. If I type more than two lines of text, only two lines are visible now requiring me to toggle up and down with the arrow keys. I checked with another user and this appears to have changed across our company. Any way to adjust the box size will the card is open? Very difficult to work in the card without the title info fully visible.

Accepted answers

Alex W_jr9vvs

Hey all, this bug has now been fixed. Can you check if titles are now appearing properly for you now? Tagging all for visibility:

@Bonnie Bright @Nina Medlock @Kimberly Wayne @Ronalds Lapsa @Keith Winkler @mistepanek

All comments

mistepanek

same problem here

Keith Winkler

I just jumped into Trello and added a new card only to find the same thing. I can only see the first line of the title. This seems to be a new bug? The entire title has always shown before.

I'm using Chrome browser on a Macbook Pro running MacOS 10.15.7.

Hopefully this will be fixed soon. We're currently a bit handicapped while having to dig to see the whole title.

Thanks!

Ronalds Lapsa

Same problem here..

Kimberly Wayne

Same issue at my firm, but not all users are experiencing the display issue.

Interim suggestion until a fix occurs is to use the arrow keys to scroll through and read/see all of the back of card title text.

Alex W_jr9vvs

Hey all! Sorry for the inconvenience here, but we've identified this as a bug and we're working on fixing it currently. I'll let you know when I have an update!