Some lines of text bounce during mouseovers
Categories
(Core :: Layout: Block and Inline, defect, P3)
Tracking
()
People
(Reporter: bugzilla, Unassigned)
References
()
Details
(Whiteboard: [sci-exclude])
Attachments
(6 files)
STR
- Go to this link;
- Move your mouse cursor just to the right of the Parameters sub-heading;
- Slowly move your mouse down toward the bottom of the page.
Expected:
Text does not shift.
Actual:
When the mouse moves over certain parts of the page, some lines shift down a pixel or two, and then shift back up once the mouse leaves the region that triggered the original shift.
Reporter | ||
Comment 2•5 years ago
|
||
Comment 3•5 years ago
|
||
I can't reproduce this on mac, linux or windows. Can you do a screenrecording?
Comment 4•5 years ago
|
||
Added it to the 69 list for now, until we have more info to determine priority
Comment 5•5 years ago
|
||
Confirmed on Win10 1903/GTX1060. 2560x1440. Dell U2515H (117.5 dpi)
Comment 6•5 years ago
|
||
Comment 7•5 years ago
|
||
Occurs with Basic, D3D11 (advanced layers), and WebRender. Even with scroll anchoring disabled.
Reporter | ||
Comment 8•5 years ago
|
||
Thanks for recording that!
Comment 9•5 years ago
|
||
Moving to layout because it's seems like it's more likely a layout problem.
Comment hidden (spam) |
Comment 11•5 years ago
|
||
I can repro this on Linux with sufficient zoom applied.
The hover is showing an anchor icon (which in this test-case it may be a tofu, since the font-face rules probably won't work).
I concur with Jeff that this is likely a layout bug.
Comment 12•5 years ago
•
|
||
Confirmed with Firefox 38. (Always looks a bit different, might depend on window size and zoom level.)
Updated•5 years ago
|
Comment 13•5 years ago
|
||
Bugzilla refuses to upload with the right content-type, so not sure if this will work.
Comment 14•5 years ago
|
||
Comment 15•5 years ago
|
||
Since the Bugzilla font doesn't load because of CORS.
Hover over the "A" to see the effect. The only thing that does is toggling vertical-align.
Changing the font or something else makes it not repro, so it seems we need the Segoe UI font.
The vertically-aligned thing has some different font and uses some different line-height. So it seems possible that it somehow changes the height of its line.
Still, it seems quite weird to me that it doesn't shift the block (the paragraph) but only some lines of it, and only if some particular font is used... Jonathan, does something like this ring a bell?
Comment 16•5 years ago
|
||
Ok, so if I put a border around the paragraph, I can see that the whole paragraph shifts some, but still at some zoom levels some lines shift more than others, which is really weird.
Comment 17•5 years ago
|
||
(On the fence between "block and inlines" and "text and fonts" :))
Comment 18•5 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #16)
Ok, so if I put a border around the paragraph, I can see that the whole paragraph shifts some, but still at some zoom levels some lines shift more than others, which is really weird.
This sounds like we're dealing with fractional-pixel line heights, and the baseline of different lines is then rounding to device pixels in inconsistent directions.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #15)
Since the Bugzilla font doesn't load because of CORS.
Just FTR, I think the reason it doesn't load is actually because of the redirection involved: the URL https://bugzilla.mozilla.org/attachment.cgi?id=9082788 does not link directly to the font file, but redirects to https://bug1570387.bmoattachments.org/attachment.cgi?id=9082788. If you use that URL in the @font-face rule, I think it'll probably load.
Comment 19•5 years ago
|
||
The priority flag is not set for this bug.
:mats, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 20•2 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE
.
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Description
•