Describe the bug
When running an Eclipse product without monitor-specific scaling (e.g., by disabling the preference or with -Dswt.autoScale.updateOnRuntime=false) and default auto-scale settings (i.e., the implicit swt.autoScale=quarter), wrong font sizes are considered at some places. This particularly includes the header size calculation of CTabFolders, which may become too large/small.
This also happens when running any pure SWT application with default auto-scale settings, such as the CustomControlExample.
It is a regression from:
To Reproduce
- Set primary monitor zoom to something different than 100% or 200% (e.g., 150%).
- Start the
CustomControlExample with default settings and go to the CTabFolder tab or start an Eclipse SDK.
- You will see that tab headers are too small.
Expected behavior
CTabFolder headers shall be sized correct.
Screenshots

Environment:
- Select the platform(s) on which the behavior is seen:
Version since
I20250714-1800
Describe the bug
When running an Eclipse product without monitor-specific scaling (e.g., by disabling the preference or with
-Dswt.autoScale.updateOnRuntime=false) and default auto-scale settings (i.e., the implicitswt.autoScale=quarter), wrong font sizes are considered at some places. This particularly includes the header size calculation ofCTabFolders, which may become too large/small.This also happens when running any pure SWT application with default auto-scale settings, such as the
CustomControlExample.It is a regression from:
To Reproduce
CustomControlExamplewith default settings and go to theCTabFoldertab or start an Eclipse SDK.Expected behavior
CTabFolderheaders shall be sized correct.Screenshots

Environment:
Version since
I20250714-1800