[Stub Installer] Wrapping text issue inside Reinstall prompt on a certain Windows 7 configuration
Categories
(Firefox :: Installer, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | affected |
People
(Reporter: asoncutean, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
132.44 KB,
image/png
|
Details |
screenshot issue.png
[Affected versions]:
- 68.0b5
[Affected platforms]:
- Windows 7 x32
[Steps to reproduce]:
- Trigger the Reinstall prompt ( make sure the same stub version was previously installed and run at least once)
[Expected result]:
- The header text is properly wrapped.
[Actual result]:
- The header text is not wrapped correctly.
[Regression range]:
- Introduced with the new UI change.
[Additional Notes]:
- I’ve reproduce this issue only with one machine and regardless the changes made on the display settings, with one exception, setting custom DPI to 200% fixes the problem.
- GPU: ATI Radeon 3000.
- I can see wrapping issue on Paveover prompt also (it locale).
|
||
Comment 1•5 years ago
|
||
Hmm. The text rendering is done by a Windows function, and I'm already telling it to break on word boundaries, so I don't know if there's much I can really do here.
Does that installation of Windows 7 have all its updates? Is the GPU driver the latest one available for that card?
|
Reporter | |
Comment 2•5 years ago
|
||
(In reply to Matt Howell (he/him) [:mhowell] from comment #1)
Does that installation of Windows 7 have all its updates? Is the GPU driver the latest one available for that card?
Yes and yes, I’ve checked that before submitting the bug.
But after further investigation this looks very edge case and I think somehow something maybe got broken on my end. I use two monitors with different native resolution (1920 x 1080, respectively 1680 x 1050). I tried to reproduce this issue on other test machines with similar configuration, using the same 1680 x 1050 monitor but without any luck. Any other Windows versions I used show no issue regarding the text wrapping.
|
|
||
Comment 3•5 years ago
|
||
Thanks for checking that and for the additional info.
To me this really feels like either a Windows or a video driver bug, and even if it isn't, I'm not sure what I could do about it (or if it would be worth it to do anyway for such an edge case problem). So I'm going to close this bug; we can reopen it if anything new turns up.
Description
•