GtkSpinButton's context menu changes the width of '+'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-themes (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
GtkSpinButton consists of a (typically numeric) input field, followed by a '-' and finally a '+' sign. The width of the '+' sign shrinks a little bit when you open the right-click context menu of the input field. It shouldn't, it should have a constant width.
Happens with Ubuntu's old default Ambiance and Radiance themes. Does not happen with Ubuntu's new default Yaru, or with GTK's default Adwaita.
Example: Open gnome-terminal, right click on its terminal canvas, choose Preferences. You're taken to the profile's Text tab which contains four such widgets. Right-click on one of these input fields, e.g. on "80" for the initial number of columns. In addition to the context menu appearing, the '+' button becomes narrower, and thus the label on its right (e.g. "columns") shifts to the left. For some of the spinbuttons (the ones that stretch the window) the entire window also shrinks. Dismiss the context menu and it goes back to its previous width.
(This is similar to former bug 1740709.)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: light-themes 19.04-0ubuntu1
ProcVersionSign
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Sep 13 11:48:51 2019
InstallationDate: Installed on 2016-11-09 (1037 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitec
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to eoan on 2019-09-08 (4 days ago)
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
See this document for currently supported Ubuntu releases: /wiki.ubuntu. com/Releases
https:/
We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.