Truncate very long text in the ticket properties dialog

[Ryan J Ollos]

Use a bit of CSS to prevent this from happening. It's a bit of a corner case because the text would have to be quite long, but will be easy to fix.

[Ryan J Ollos <ryan.j.ollos@…>]

I see 3 options here.

1. Truncate long text that doesn't break normally.
2. Don't truncate, rather force words to break.
3. Force all text to truncate and don't break any text.

trac/htdocs/css/ticket.css

@@ -101 +101 @@
  width: 20%;
 }
 #ticket table.properties th.missing { color: #d3d398; }
-#ticket table.properties td { width: 30% }
+#ticket table.properties td {
+ overflow: hidden;
+ text-overflow: ellipsis;
+ width: 30%;
+}
 #ticket table.properties td p:first-child { margin-top: 0 }
 #ticket table.properties td p:last-child { margin-bottom: 0 }
 #ticket table.properties .description { border-top: 1px solid #dd9 }

---

trac/htdocs/css/ticket.css

@@ -101 +101 @@
  width: 20%;
 }
 #ticket table.properties th.missing { color: #d3d398; }
-#ticket table.properties td { width: 30% }
+#ticket table.properties td {
+ width: 30%;
+ word-break: break-all;
+}
 #ticket table.properties td p:first-child { margin-top: 0 }
 #ticket table.properties td p:last-child { margin-bottom: 0 }
 #ticket table.properties .description { border-top: 1px solid #dd9 }

trac/htdocs/css/ticket.css

@@ -101 +101 @@
  width: 20%;
 }
 #ticket table.properties th.missing { color: #d3d398; }
-#ticket table.properties td { width: 30% }
+#ticket table.properties td {
+ overflow: hidden;
+ text-overflow: ellipsis;
+ width: 30%;
+ white-space: nowrap;
+}
 #ticket table.properties td p:first-child { margin-top: 0 }
 #ticket table.properties td p:last-child { margin-bottom: 0 }
 #ticket table.properties .description { border-top: 1px solid #dd9 }

[Ryan J Ollos <ryan.j.ollos@…>]

Btw, my preference is (3), since there is plenty of room for text of reasonable length and enough characters to infer the actual name even in the case of truncation.

[Christian Boos]

With the white-space: nowrap in 3), you'd not see all the people in CC:, you'd not see all the keywords, etc. I think it's not OK.

Then between 1) and 2), I think I prefer 2), in order to not lose information. Otherwise the only place in the page where you could see the full content for the field is where it has been set in the change history.

[Ryan J Ollos <ryan.j.ollos@…>]

I hadn't given this enough thought and considered CC and keywords, so I would agree that (3) is not okay. As to (1) or (2) then, I have no preference. If we truncated, we could show the full name on hover-over, but you are probably right that it's better to just not truncate.

[Ryan J Ollos]

We should also deal with the possibility of very long text in the author field of a comment. Here is a screen capture from t-h.o:

[Ryan J Ollos]

Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.

[Ryan J Ollos]

Milestone renamed