about:telemetry - better adjust media querries so that Section names don't touch elements from right side of page on resize/zoom
Categories
(Toolkit :: Telemetry, defect, P3)
Tracking
()
People
(Reporter: cfogel, Assigned: patrickmcghen, Mentored)
Details
(Whiteboard: [good second bug][lang=css])
Attachments
(3 files)
Affected versions
- 89.0a1(2021-03-28), 88.0b2;
Affected platforms
- Ubuntu 20, Windows 10;
Steps to reproduce
- Launch Firefox, access about:telemetry#scalars-tab
- Grab the browser and shrink its width gradualy;
Expected result
- page elements don't get overlapped and have spacing across various sizes;
Actual result
- Scalars(section name) touches Current Store(element from right side of page) on certain page-widths;
- main issue being that text is next to text;
Regression range
- will check and provide one asap;
Additional notes
- attached screenshot to best illustrate the issue;
- same for Keyed Scalars, Histograms, Keyed Histograms;
Reporter | ||
Updated•4 years ago
|
Comment 1•4 years ago
|
||
It is very likely this extends back very far (back to about:telemetry's redesign in the summer of 2017), so it need not have a firm regression range.
Comment 2•3 years ago
|
||
Hey, I wanted to propose a fix for this issue (it's very small but I think it should do the trick) but when I try to push I am asked to merge it with another head as I cannot create a new one. I'm not entirely sure how best to manage this?
Comment 3•3 years ago
|
||
(In reply to maaike.dumont from comment #2)
Hey, I wanted to propose a fix for this issue (it's very small but I think it should do the trick) but when I try to push I am asked to merge it with another head as I cannot create a new one. I'm not entirely sure how best to manage this?
Hey, you will need an account on https://phabricator.services.mozilla.com/ and then use moz-phab to submit your changes. See the Phabricator User Guide for details.
Comment 4•3 years ago
|
||
Yes I have an account and also did moz-phab install-certificate but it's still not letting me push anything. Tempted to just do a clean install after work :)
Updated•3 years ago
|
Updated•3 years ago
|
Comment 6•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee | ||
Comment 7•2 years ago
|
||
I'd like to finish this one up.
Comment 8•2 years ago
|
||
By all means, please do! If you submit a patch, the bots ought to assign this bug to you.
Assignee | ||
Comment 9•2 years ago
|
||
Updated•2 years ago
|
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Updated•2 years ago
|
Comment 12•2 years ago
|
||
Reproduced this issue on an affected Nightly build from 2021-03-29, using the STR from Comment 0 on Win 10.
Verified as fixed on Firefox 112.0b9 (20230330182947) and Firefox 113.0a1 (20230403092724) across the following platforms: Win 10 x64, Ubuntu 20.04 and macOS 10.15.
Description
•