Opened 7 years ago
Closed 5 years ago
#12946 closed defect (fixed)
Don't issue empty <dd> comment block in timeline
Reported by: | Dirk Stöcker | Owned by: | Jun Omae |
---|---|---|---|
Priority: | normal | Milestone: | 1.2.4 |
Component: | timeline | Version: | 1.2.2 |
Severity: | minor | Keywords: | |
Cc: | Branch: | ||
Release Notes: |
Fixed instance of empty comment block in timeline. |
||
API Changes: | |||
Internal Changes: |
Description
When the timeline contains entries without comment, then an empty <dd> block is created. Tidy complains about these.
Please simply don't create empty <dd>. Saves spaces and reduces the warnings.
Attachments (0)
Change History (10)
comment:1 by , 7 years ago
Component: | general → timeline |
---|---|
Milestone: | → 1.2.3 |
Owner: | set to |
Status: | new → assigned |
comment:2 by , 7 years ago
Yes. Fixes the issue. A side effect is that also the separating space is removed.
A fix for this style issue:
-
trac/htdocs/css/timeline.css
old new 45 45 .timeline dt .time { color: #999; font-size: 80%; } 46 46 .timeline dt .trac-author { color: #666; } 47 47 .timeline dt.highlight { background-color: #ffa; } 48 .timeline dt.nocomment { margin-bottom: .75em; } 48 49 .timeline dd { 49 50 font-size: 80%; 50 51 margin: 0 0 .75em 5.8em;
And the <dt> class in above snippet must look like:
<dt class="${classes(event.kind, highlight=highlight, unread=unread, nocomment=False if rendered else True)}">
comment:3 by , 7 years ago
I'd like to use dt + dt
selector rather than .nocomment
selector.
-
trac/htdocs/css/timeline.css
diff --git a/trac/htdocs/css/timeline.css b/trac/htdocs/css/timeline.css index 8097df11c..f7c8279f5 100644
a b 23 23 } 24 24 25 25 .timeline dt { background: 3px 4px no-repeat; padding: 0 } 26 .timeline dt + dt { margin-top: 0.75em } 26 27 .timeline dt :link, .timeline dt :visited { 27 28 background: 3px 3px no-repeat; 28 29 border: none;
comment:5 by , 6 years ago
Milestone: | 1.2.3 → 1.2.4 |
---|
comment:6 by , 6 years ago
Milestone: | 1.2.4 → 1.2.5 |
---|
comment:7 by , 6 years ago
Any reason why this isn't simply applied instead of moving it from milestone to milestone?
comment:9 by , 6 years ago
So you leave a bug open for 11 months because you feel a unit test is required to check if a buggy feature really is properly fixed?
I could agree that unit tests are mandatory for new features, but not for bug fixes! So if you have a security hole and get a fix will you also reject it for a year due to missing unit test?
comment:10 by , 5 years ago
Milestone: | 1.2.5 → 1.2.4 |
---|---|
Release Notes: | modified (diff) |
Resolution: | → fixed |
Status: | assigned → closed |
Reproduced it when attaching a file without comment.
Please try the following patch:
trac/timeline/templates/timeline.html