After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 448896 - Inconsistent "Minimum font size" settings
Inconsistent "Minimum font size" settings
Status: RESOLVED DUPLICATE of bug 336152
Product: epiphany
Classification: Core
Component: Interface
2.19.x
Other All
: Normal minor
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2007-06-18 20:17 UTC by freggy1
Modified: 2007-07-28 16:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description freggy1 2007-06-18 20:17:54 UTC
Please describe the problem:
In the menu Edit - Preference in the tab page Fonts & Style, there is a setting called "Minimum size". When you click on the button "Detailed Font Settings...", there's again a setting "Minimum Size". Both settings seem to work completely idependently. Either they are both the same setting, and in that case they should always show the same value, either they are something different, but then the label should be changed so it's clear that these settings are not the same.

Steps to reproduce:
1. Go to Edit - Preference, tab page Fonts & Style
2. Modify Minimum Size, for example change it from 9 to 12
3. Click on "Detailed Font Settings..." 


Actual results:
Mimimum size shows another value than 12. When changing the Minimum size in Detailed Font Settings, the minimum size in the previous tab page is not changed either.

Expected results:
Both should show exactly the same value or the label should be different.

Does this happen every time?


Other information:
Problem exists in 2.18 and 2.19
Comment 1 Martin Ejdestig 2007-07-28 16:38:48 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 336152 ***