[linux] Icons from List all tabs are moving after opening
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox109 | --- | wontfix |
| firefox110 | --- | wontfix |
| firefox111 | --- | wontfix |
People
(Reporter: atrif, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
1.25 MB,
image/gif
|
Details |
Found in
- 110.0b2
Affected versions
- 111.0a1 (20230118095131)
- 110.0b2
- 190.0RC2
Tested platforms
- Affected platforms: Ubuntu 20.04
- Unaffected platforms: Windows 10x64, macOS 10.15
Steps to reproduce
- Open Firefox and some random pages in new tabs.
- Click on the List all tabs button and observe the icons.
Expected result
- The icons are no moving after the drop-down is opened.
Actual result
- The icons are moving after the drop-down is opened.
Regression range
- Last good revision: 8108291015f4419be14591ead2d59d6235e7e601
First bad revision: 73dd9b390b9a0712ea44b2345966c54ebc83c492
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8108291015f4419be14591ead2d59d6235e7e601&tochange=73dd9b390b9a0712ea44b2345966c54ebc83c492
Additional notes
- Attached a screen recording of the issue.
| Reporter | ||
Comment 1•2 years ago
|
||
Hello Emilio! Mozregression pointed out these patches, do you know which one can be the regressor? Thank you!
Updated•2 years ago
|
Comment 2•2 years ago
|
||
I can't repro this but those patches are interdependent so let's go with the first (bug 1799343)
Comment 3•2 years ago
|
||
Based on comment #1, this bug contains a bisection range found by mozregression. However, the Regressed by field is still not filled.
:emilio, since you are the author of the changes in the range, if possible, could you fill the Regressed by field and investigate this regression?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 4•2 years ago
|
||
I can't reproduce either, for what it's worth. I wonder what setting we're missing.
Alexandru: in the Ubuntu settings app, "Displays" section, do you have "Scale" set to something other than 100%? If so, it'd be useful to know the specific value you're using there.
| Reporter | ||
Comment 5•2 years ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #4)
I can't reproduce either, for what it's worth. I wonder what setting we're missing.
Alexandru: in the Ubuntu settings app, "Displays" section, do you have "Scale" set to something other than 100%? If so, it'd be useful to know the specific value you're using there.
I can reproduce the issue on a Ubuntu 20.04 VM (1600x1200 / 100% scale) and on Ubuntu 20.04 (1920x1080 / 100% scale) psychically installed on a laptop. If more information is needed please let me know.
Comment 6•2 years ago
|
||
Thanks. For what it's worth: I'm using (and unable to reproduce) on Ubuntu 22.04, whereas you mentioned reproducing on 20.04.
I wonder if this bug is specific to 20.04 -- possibly even just because of subtle theme/UI-sizing differences between the two releases, which manifest as a rounding difference in 20.04.
I'll try to test in a v20.04 VM at some point soon, to see if that helps me reproduce. If you happen to have 22.04 available for testing, it'd be great to know if you can repro there, too.
| Reporter | ||
Comment 7•2 years ago
•
|
||
(In reply to Daniel Holbert [:dholbert] from comment #6)
Thanks. For what it's worth: I'm using (and unable to reproduce) on Ubuntu 22.04, whereas you mentioned reproducing on 20.04.
I wonder if this bug is specific to 20.04 -- possibly even just because of subtle theme/UI-sizing differences between the two releases, which manifest as a rounding difference in 20.04.
I'll try to test in a v20.04 VM at some point soon, to see if that helps me reproduce. If you happen to have 22.04 available for testing, it'd be great to know if you can repro there, too.
You are right. I think this may be specific to Ubuntu 20.04. I tried reproducing this on Ubuntu 22.04 using Firefox 111.0a1 (2023-01-13) but the issue does not reproduce with Wayland.
| Reporter | ||
Comment 8•2 years ago
•
|
||
(In reply to Alexandru Trif, QA [:atrif] from comment #7)
(In reply to Daniel Holbert [:dholbert] from comment #6)
Thanks. For what it's worth: I'm using (and unable to reproduce) on Ubuntu 22.04, whereas you mentioned reproducing on 20.04.
I wonder if this bug is specific to 20.04 -- possibly even just because of subtle theme/UI-sizing differences between the two releases, which manifest as a rounding difference in 20.04.
I'll try to test in a v20.04 VM at some point soon, to see if that helps me reproduce. If you happen to have 22.04 available for testing, it'd be great to know if you can repro there, too.
You are right. I think this may be specific to Ubuntu 20.04.I tried reproducing this on Ubuntu 22.04 using Firefox 111.0a1 (2023-01-13) but the issue does not reproduce with Wayland.
Sorry for the spam.... It seems that I can reproduce the issue on Ubuntu 22.04 as well with Firefox 111.0a1 (2023-01-13) if I start Firefox with export MOZ_ENABLE_WAYLAND_0 and Window Protocol is set to xwayland.
Comment 9•2 years ago
•
|
||
Thanks - yeah, I can repro on Ubuntu 22.04 if I simply log in with Xorg instead of Wayland (using the gear icon at bottom right of login screen that appears when the password-entry field is up), or if I start Firefox with the MOZ_ENABLE_WAYLAND=0 environmental variable.
Updated•2 years ago
|
Description
•