Closed
Bug 136003
Opened 22 years ago
Closed 22 years ago
two extra spaces after every comment
Categories
(Bugzilla :: Bugzilla-General, defect, P3)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.16
People
(Reporter: bbaetz, Assigned: bbaetz)
Details
(Keywords: regression)
Attachments
(1 file)
650 bytes,
patch
|
gerv
:
review+
gerv
:
review+
|
Details | Diff | Splinter Review |
comments.tmpl has: <pre> [%- quoteUrls(comment.body) -%] </pre> I added the - bits to stop new lines, but it still adds the spaces, since the generated html is: <pre>asda </pre> This is because PRE_CHOMP removes whitespace back to the end of the preceeding line, but POST_CHOMP (which we don't use by default for some reason I don't really understand) only chomps to the beginning of teh next line. The fix is to just move this all only one single line, so I'll attach the trivial patch.
Assignee | ||
Comment 1•22 years ago
|
||
The alternate fix is to just move the <pre> and its contents onto one single line.
Assignee | ||
Updated•22 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.16
Comment 2•22 years ago
|
||
Is there a reason not to turn on POST_CHOMP? Why is PRE and POST asymmetric? I this worth worrying about?
Assignee | ||
Comment 3•22 years ago
|
||
apparently it was so that templates were easy to look at to debug. post and pre aren't really different - PRE removes stuff before the directive onthe same line, and POST removes stuff after the directive on teh same line. POST_ wouldn't help here, though, because of that - that was just a side issue I mentioned in passing.
Comment 4•22 years ago
|
||
Comment on attachment 78070 [details] [diff] [review] v1 2xr=gerv. The reason we don't use POST_CHOMP as well as PRE_CHOMP is that then the generated HTML would be all on one line (mostly) rather than the reasonably-nicely-formatted stuff we produce at the moment. This would make templates a lot harder to debug. Gerv
Attachment #78070 -
Flags: review+
Assignee | ||
Comment 5•22 years ago
|
||
Yeah, but we can still turn it off privately for debugging. I predict that there are more bugzilla page views which are not debugging than those that are... Anyway, checked in
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•