Closed Bug 646769 Opened 13 years ago Closed 13 years ago

format AppNotes and Winsock_LSP fields so newlines are readable

Categories

(Socorro :: Webapp, task)

x86
Windows 7
task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: timeless, Assigned: espressive)

References

()

Details

attachment 523181 [details] shows an unreadable list of lsp's

please add a <br> after each.

try to read the lsp list in bp-fe71aa56-071d-4fbe-a04b-1ae592110319

you can't.

see bug 613874 comment 9 where stephend tried to help me by pointing out that the underlying data was ok
Presumably we could either s/\n/<br>/g or stick the whole thing in a <pre>.
Summary: please add a <br> after each lsp → format AppNotes field so newlines are readable
Summary: format AppNotes field so newlines are readable → format AppNotes and Winsock_LSP fields so newlines are readable
Assignee: nobody → sneethling
Target Milestone: --- → 2.4
Sent pull request: https://github.com/mozilla/socorro/pull/210

Test Case
----------

Head to an individual report page such as here:
https://espressive-dev.allizom.org/report/index/ca02bcc1-5272-4f0d-a2f1-d8a1a2111204

On the first table look for the row with the side header AppNotes and Winsock-LSP. The content in the right hand content cells should no longer be one long string but, separated appropriately on new lines.
Status: NEW → ASSIGNED
Commit pushed to https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/f8e875a74124a31060fb5bf9422da63f896b1b86
Merge pull request #210 from ossreleasefeed/bug646769-make-appnotes-winsock-readable

added pre tags to make appnotes and winsock content more readable :: fixes bug 646769
Target Milestone: 2.4 → ---
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.4
Component: Socorro → General
Product: Webtools → Socorro
Component: General → Webapp
Verified on prod ... looks like this slipped into the 3.5 release by accident.
Status: RESOLVED → VERIFIED
Target Milestone: 2.4 → 2.3.5
You need to log in before you can comment on or make changes to this bug.