Hovering tabs in about:certificate can cause the most of the text on the page to jump
Categories
(Firefox :: Security, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr78 | --- | unaffected |
| firefox82 | --- | unaffected |
| firefox83 | --- | wontfix |
| firefox84 | --- | verified |
| firefox85 | --- | verified |
People
(Reporter: itiel_yn8, Assigned: emilio)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files)
STR:
- Open the certificate page for https://english.president.gov.tw/
- Hover the second tab ("政府伺服器數位憑證管理中心 - G1")
- See the text on the page jumps up and down while you hover in and out
Comment 2•5 years ago
|
||
Set release status flags based on info from the regressing bug 1669857
Comment 3•5 years ago
|
||
Hmm I can't reproduce. Could be a layout issue? Let's keep it in this component for now...
(In reply to Johann Hofmann [:johannh] from comment #3)
Hmm I can't reproduce. Could be a layout issue? Let's keep it in this component for now...
Sigh. Of course it had to be a DPI-related issue...
This is fixed for me if I bump the border and padding to 4px and 16px respectively. I've verified this works across 125%, 150% and 175% (and of course 100%).
johannh, is this an acceptable solution?
Comment 5•5 years ago
|
||
Hmm that's probably fine as a workaround in this instance, yeah, though I do wonder if we should file another bug with Layout, since this page shouldn't get rendered differently than web content so there may be a larger-scale bug here?
| Assignee | ||
Comment 6•5 years ago
|
||
See https://crisal.io/words/2020/06/13/rounding-borders.html for why
border and padding snap differently, and the trade-offs we make.
This should also be faster (should avoid needing a re-layout).
Updated•5 years ago
|
| Assignee | ||
Comment 7•5 years ago
|
||
(In reply to Johann Hofmann [:johannh] from comment #5)
Hmm that's probably fine as a workaround in this instance, yeah, though I do wonder if we should file another bug with Layout, since this page shouldn't get rendered differently than web content so there may be a larger-scale bug here?
Working as intended I'd say.
Comment 9•5 years ago
|
||
| bugherder | ||
Comment 10•5 years ago
|
||
I managed to reproduce the issue using an older version of Nightly (2020-10-21) on Windows 10 x64.
I retested everything using latest Nightly 85.0a1 and Firefox 84.0b3 on Windows 10 x64, Ubuntu 16.04 x64 and macOS 11.0.1. The issue is not reproducing anymore.
Updated•5 years ago
|
Description
•