Open
Bug 1476254
Opened 6 years ago
Updated 2 years ago
[DevTools] - treemap text overlap tree lines
Categories
(DevTools :: Memory, defect, P3)
DevTools
Memory
Tracking
(firefox-esr52 wontfix, firefox-esr60 fix-optional, firefox61 wontfix, firefox62 wontfix, firefox63 wontfix, firefox64 wontfix, firefox65 fix-optional)
NEW
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | wontfix |
firefox-esr60 | --- | fix-optional |
firefox61 | --- | wontfix |
firefox62 | --- | wontfix |
firefox63 | --- | wontfix |
firefox64 | --- | wontfix |
firefox65 | --- | fix-optional |
People
(Reporter: cfogel, Unassigned)
Details
(Keywords: regression)
Attachments
(1 file)
30.55 KB,
image/png
|
Details |
[Affected versions]: - Firefox 61.0.1, 62.0b9, 63.0a1 (2018-07-16) [Affected platforms]: - Win 8x32, Win 10x64, macOS 10.13.4, Ubuntu 16.04LTS; [Steps to reproduce]: 1. Launch firefox; 2. Navigate to: https://www.irfanview.com/eula.htm 3. Open the devTools; 4. Click on the Memory tab; 5. Click on the Take Snapshot button. [Expected result]: - content is properly displayed. [Actual result]: - text in the first tree-map area is overlapping with tree-lines; [Regression range]: - best regression range after mozregression bisection: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=91115264629dfaacf2d60d52a3eff89c18c5af0d&tochange=afd82f887093e5e9e4015115ca5795ec82a6f732 last good: 91115264629dfaacf2d60d52a3eff89c18c5af0d (2016-04-14) first bad: afd82f887093e5e9e4015115ca5795ec82a6f732 (2016-04-15) [Additional notes]: - attached screenshot with the issue; - win_7(both 32/64) seems not to be affected; - on 49.0a1 (2016-04-25) the last section(one on the right) was affected;
Reporter | ||
Updated•6 years ago
|
Keywords: regression
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Comment 1•5 years ago
|
||
Unassigned P3, so wontfix for 64.
Comment 2•5 years ago
|
||
Happy to take a patch in nightly; if it seems low risk enough please feel free to request uplift to 65 beta.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•