Closed
Bug 1236529
Opened 9 years ago
Closed 9 years ago
Fix about:telemetry ping rendering & updating when changing views & reloading
Categories
(Toolkit :: Telemetry, defect, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
mozilla46
| Tracking | Status | |
|---|---|---|
| firefox46 | --- | fixed |
People
(Reporter: gfritzsche, Assigned: gfritzsche)
References
Details
(Keywords: regression, Whiteboard: [measurement:client])
Attachments
(1 file)
|
18.08 KB,
patch
|
Dexter
:
review+
|
Details | Diff | Splinter Review |
STR:
* go to about:telemetry
* choose "archived ping"
* choose "raw json" display
* reload
Expected:
Raw ping display.
Actual:
A "null" line, followed by the structured ping display.
| Assignee | ||
Updated•9 years ago
|
Assignee: nobody → gfritzsche
Points: --- → 1
Priority: P2 → P1
| Assignee | ||
Comment 2•9 years ago
|
||
This fixes the ping rendering updating issues i see here, from reloading to flipping through views and archived pings. Would be happy to have a second look at it by you though. One thing im not so happy about is how PingPicker.update() looks now, but i dont think it can be improved too much without any bigger refactoring (and we need the change tracking there to not lose states all the time).
Attachment #8704573 -
Flags: review?(alessio.placitelli)
| Assignee | ||
Updated•9 years ago
|
Summary: Reloading about:telemetry shows "null" raw ping data section → Fix about:telemetry ping rendering & updating when changing views & reloading
Comment 3•9 years ago
|
||
Comment on attachment 8704573 [details] [diff] [review]
Fix about:telemetry ping rendering
Review of attachment 8704573 [details] [diff] [review]:
-----------------------------------------------------------------
This looks good. I agree with you, I'm not sure this could look much better without a refactoring.
Attachment #8704573 -
Flags: review?(alessio.placitelli) → review+
Comment 5•9 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla46
You need to log in
before you can comment on or make changes to this bug.
Description
•