Find input on settings page
Categories
(Thunderbird :: Preferences, defect)
Tracking
(Not tracked)
People
(Reporter: bugzilla, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [closeme 2024-07-25])
Attachments
(1 file)
|
316.53 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0
Steps to reproduce:
After re-installing my laptop with Ubuntu 24.04 and Thunderbird 128.0b1, the find input box on the settings page is partially off the right hand side of the displayed window. See attached screenshot.
Comment 1•2 years ago
|
||
Hello,
I tried to reproduce this issue using the affected build from 2024-06-21(20240621222440) using Ubuntu 24.04 and Ubuntu 22.04 but did not manage to reproduce it.
I have also tried to reproduce it using 128.0b1(20240611161651), the latest ESR 128.0(20240703144221) but to no avail.
Could you give us more information in order for us to properly reproduce this behaviour(resolution used, multiple monitor layout, accessibility settings-if any, etc)
Are you still able to reproduce this issue with the same repro steps?
| Reporter | ||
Comment 2•2 years ago
|
||
Hello Vlad,
My screen resolution is 3840x2160 (4k). The only display is my laptop screen, which is 14 inches. I have 300% screen scaling set in the Ubuntu settings. Maybe the screen scaling triggers the problem? The only accessibility setting I have enabled is "reduced animations".
Comment 3•2 years ago
•
|
||
Hello,
I have tried to reproduce your issue again using the new information provided and still could not reproduce it.
I have used the 3840x2160 resolution, alongside a 300% screen scaling (although my screen size is 17inches).
Also went through different other resolutions and scaling options (including fractional scaling option with different values) on both Ubuntu 22 and 24.
If you can still reproduce this issue with the same repro steps, it would very helpful if you could indicate the affected versions on which you are able to reproduce it(besides the 128.0b1 on which you have encountered it) and if time allows, help us with a regression range for this issue.
I will provide the steps necessary.
You have to determine a build that reproduces the issue. In your case it seems Thunderbird v128.0b1 (64-bit), right? You can retest it anytime.
Then you should find one that does NOT reproduce it. Detailed steps:
a. Open Mozregression app;
b. Click "File" -> "Run a single build";
c. On the "Single Run Wizard" pop-up, "Basic configuration", select "Thunderbird" and click "Next".
d. On the "Profile selection" page, just click the "Next" button.
e. On the "Build selection" select a date (dates before 2024-06-21 to have a better chance finding one that does not reproduce the issue) from the drop-down on the left and click "Finish".
f. Now the mozregression app will open a thunderbird build of the selected date and you can use it, close it and open another. (make a note of the version that does not reproduce the issue)
You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
a. Open mozregression-gui.exe
b. Click "File" -> "Run a new bisection"
c. On "Basic configuration" screen, select "Thunderbird" and click "Next" button.
d. Skip "Profile selection" screen by the "Next" button.
e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found NOT to reproduce the issue.
e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found to reproduce the issue.
f. Click "Finish" to start the bisection process.
g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.
Copy the logs in a text file and attach it to this bug.
If there is still information you need regarding the regression process, please request information from me.
Thank you for your contribution!
Comment 4•2 years ago
|
||
Alistair, this is still happening with newer beta? And didn't happen with beta 127?
Updated•2 years ago
|
Updated•2 years ago
|
Description
•