Open
Bug 361281
Opened 18 years ago
Updated 15 years ago
Long nickname table nesting should not include timestamp
Categories
(Other Applications :: ChatZilla, defect)
Other Applications
ChatZilla
Tracking
(Not tracked)
NEW
People
(Reporter: bugzilla-mozilla-20000923, Assigned: rginda)
References
()
Details
(Keywords: polish, regression)
See http://twpol.dyndns.org/temp/cz_ts_1.png for the visual result of this bug. When we have a long nickname, we basically insert this row into the table:
<tr class="msg-nested-tr"><td colspan="3" class="msg-nested-td">
and put the normal row inside there (with a wrapper table/tbody).
The problem, as is clear from the image, is that we lose the width of the timestamp column if there is no text in it. The solution is to only put the nickname and text cells into the nested table.
Reporter | ||
Updated•18 years ago
|
Assignee: rginda → silver
Reporter | ||
Comment 1•18 years ago
|
||
Alright, so to update this slightly: we can't keep the nickname column outside the nested table, since that would mess up vertical alignment of the timestamps when we use the same nested table for multiple lines (collapsing).
That means, the only option is to - somehow - enforce the width of the timestamp cell. If we're showing all timestamps, it isn't an issue, but perhaps we could always insert the timestamp into the first row of a nested table, and just visibility: hidden; it?
Reporter | ||
Updated•15 years ago
|
Assignee: silver → rginda
Reporter | ||
Updated•15 years ago
|
QA Contact: samuel → chatzilla
Comment 2•15 years ago
|
||
Is this not fixed? I tried it just now, can't reproduce. :-(
Reporter | ||
Comment 3•15 years ago
|
||
It's definitely still broken, looks exactly like the original screenshot too.
You need to log in
before you can comment on or make changes to this bug.
Description
•