Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Nebula new tiles are too wide

  • 2 răspunsuri
  • 1 are această problemă
  • 9 vizualizări
  • Ultimul răspuns de sfhowes

more options

My Thunderbird just upgraded to v128.2esr Nebula

I was using Cards view and it was nice, but it seems the Cards just got wider vertically. They used to be 2 lines of height, and now they are 3 lines.

As I understand, the 3rd lines is only used to display "X replies", but I use the "Unthreaded" sort option, so the 3rd line is always empty for me, and takes more space for nothing.

As you know, vertical screen estate is limited with our 16:9 screen, so please give us an option to reduce the cards view vertical size (or have it automatically remove that 3rd line in Unthreaded view)

thanks

My Thunderbird just upgraded to v128.2esr Nebula I was using Cards view and it was nice, but it seems the Cards just got wider vertically. They used to be 2 lines of height, and now they are 3 lines. As I understand, the 3rd lines is only used to display "X replies", but I use the "Unthreaded" sort option, so the 3rd line is always empty for me, and takes more space for nothing. As you know, vertical screen estate is limited with our 16:9 screen, so please give us an option to reduce the cards view vertical size (or have it automatically remove that 3rd line in Unthreaded view) thanks

Toate răspunsurile (2)

more options

I ended up making a userChrome.css with:

html|tr[is="thread-card"] { height: 44px !important; } html|div.thread-card-last-row { margin-top: -1.2em !important; }

more options

Your css works fine, although I trimmed some parts to make it work without any html declarations at the top of the userChrome:

[is="thread-card"] {
	height: 44px !important;
}
div.thread-card-last-row {
	margin-top: -1.2em !important;
}


See also this topic.