[UI] Long strings breaks layout on report index

VERIFIED FIXED in 5

Status

VERIFIED FIXED
7 years ago
7 years ago

People

(Reporter: espressive, Assigned: espressive)

Tracking

unspecified

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(2 attachments)

(Assignee)

Description

7 years ago
Created attachment 610562 [details]
screen shot of described behavior

On the report/index pages long strings are not wrapping and hence causes the tables to extend well past it's container's border. See screen shot attached.
(Assignee)

Updated

7 years ago
Summary: Long strings breaks layout on report index → [UI] Long strings breaks layout on report index
(Assignee)

Comment 1

7 years ago
Sent pull request :: https://github.com/mozilla/socorro/pull/474

TEST CASE
---------

As can be seen in the original attachment to this bug, often times the displayed signatures will far exceed 80 characters and cause the tables to break out of it's container.

The fix for this ensures that displayed signatures will never be more than 80 characters ensuring that the layout stays in tact. The full signature will always still be available when hovering over the cell containing the signature.

You can test this on pages for individual crash reports (report/index)

Comment 2

7 years ago
Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/cf987f68bef1e35649a9830646640fc669dd3d35
Merge pull request #474 from ossreleasefeed/long-signatures-breaks-layout-740392

Ensuring that displayed signature strings never exceed 80 characters fixes bug 740392

Updated

7 years ago
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Created attachment 612918 [details]
qa - verified

QA verified on stage - the character limit is 80 for signatures in the reports table at which point the full signature is viewable by hovering over the text.

Nice fix espressive - the reports page looks clean again

Updated

7 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.