Closed
Bug 1471510
Opened 7 years ago
Closed 7 years ago
[Remote Settings] The View entry details text from History tab in Admin is truncated
Categories
(Cloud Services :: Server: Remote Settings, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rdoghi, Assigned: leplatrem)
Details
Attachments
(1 file)
47.11 KB,
image/png
|
Details |
[Affected versions]:
Nightly 63.0a1
[Affected platforms]:
Platforms: Windows 10 x 64, Windows 10 x 86, Mac OS X 10.12
Preconditions :
[Steps to reproduce]:
1. Login to Kinto Admin: https://kinto-writer.stage.mozaws.net/v1/admin/
2. Reach the main-workspace bucket / product-integrity collection.
3. Reach the History tab.
4. Click the "View Entry Details" (the eye) button
Expected Result:
A Horizontal scrollbar should appear and the text should be displayed properly.
Actual Results:
The Text from View Entry Details is truncated.
Assignee | ||
Comment 1•7 years ago
|
||
Mago, would you have some bandwidth for that kind of minor bugs ?
Flags: needinfo?(magopian)
Comment 2•7 years ago
|
||
I filed https://github.com/Kinto/kinto-admin/issues/562
It seems to be a regression, I have a personal instance of kinto-admin on kinto.agopian.info which has version 1.14 and doesn't have this issue (it displays the diff "over" all the other columns, and has a "overflow: auto").
I'll investigate when this was introduced, and follow-up in the github issue.
Flags: needinfo?(magopian)
Comment 3•7 years ago
|
||
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•7 years ago
|
||
Unfortunately we can't consider this solved so easily :)
Now that the fix was fixed upstream, we still have to:
- cut out a new release of Kinto Admin
- upgrade Kinto Admin in Kinto
- release Kinto
- upgrade Kinto in kinto-dist
- release kinto-dist
- deploy kinto-dist in PROD
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•7 years ago
|
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•7 years ago
|
||
I have retested this issue and I can confirm it as fixed, i will mark it accordingly.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•