Closed
Bug 482582
Opened 16 years ago
Closed 14 years ago
Missing a line break before "Actual Results:" (or after the content of "Steps to Reproduce:") in new bug reports
Categories
(bugzilla.mozilla.org :: General, defect)
bugzilla.mozilla.org
General
Tracking
()
RESOLVED
FIXED
People
(Reporter: helder.magalhaes, Assigned: gerv)
References
()
Details
(Whiteboard: bmo4.0-resolved)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729)
Build Identifier:
"Actual Results:" is glued together with the last text entered in "Steps to Reproduce:" for newly created bug reports. Inserting a line break before (or after the content of "Steps to Reproduce:") would both increase visual consistency and potentially make bug analysis slightly faster.
Reproducible: Always
Steps to Reproduce:
1. Create a new bug report using the form at the bug's URL;
2. Fill in the fields;
3. Submit the bug report.
Actual Results:
"Actual Results:" is glued together with the last text entered in "Steps to Reproduce:"
Expected Results:
A line break would precede "Actual Results:"
Instead of trying to reproduce, which can be a bad idea since it involves creating a new issue, I'd suggest taking a look at previously reported issues such as bug 481869 and bug 480844, which show the symptom. This report will most likely also suffer from the issue being reported.
Reporter | ||
Comment 1•16 years ago
|
||
I've confirmed (while filing bug 489564) that artificially adding a like break in "Steps to Reproduce:" contents doesn't help working around the issue: something which is somehow expected, as probably a trim white-space is made during form processing.
Updated•14 years ago
|
Assignee: nobody → gerv
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•