diff options
author | Eric Williams | 2017-07-06 19:45:30 +0000 |
---|---|---|
committer | Eric Williams | 2017-07-06 20:52:23 +0000 |
commit | 4c26a2a551b3e1ab2cd1b7ee5fb43d4b6dfd5c43 (patch) | |
tree | 6d6fbb0777e79c562f0352903664be7b614f966c /pom.xml | |
parent | 21604b776e61752285a33d08fe8affd26ec9c2bd (diff) | |
download | eclipse.platform.swt-4c26a2a551b3e1ab2cd1b7ee5fb43d4b6dfd5c43.tar.gz eclipse.platform.swt-4c26a2a551b3e1ab2cd1b7ee5fb43d4b6dfd5c43.tar.xz eclipse.platform.swt-4c26a2a551b3e1ab2cd1b7ee5fb43d4b6dfd5c43.zip |
Bug 519321: [GTK3] Preferences window sometimes has white background
In Control.setBackgroundGdkRGBA(): if the incoming GdkRGBA is null, then
the background color needs to be reset to COLOR_WIDGET_BACKGROUND.
On GTK3.16+ there is an automatic check with GTK CSS to set incoming
GdkRGBA's as COLOR_WIDGET_BACKGROUND if they are null. Setting a null
GdkRGBA using GtkStyleContext machinery resets the current color to its
previous value, which now (after bug 477950) could sometimes be
transparent. This is what was causing the bug. The fix is to set
incoming GdkRGBA's that are null to COLOR_WIDGET_BACKGROUND. Of course
not every widget uses COLOR_WIDGET_BACKGROUND as the default, so it's
been overriden in those places.
This ensures GTK3.14 and below still works correctly when
setBackground(null) is called.
Change-Id: Ib635be9ed61edf8c8e602fe3e27dd8c418210b12
Signed-off-by: Eric Williams <ericwill@redhat.com>
Diffstat (limited to 'pom.xml')
0 files changed, 0 insertions, 0 deletions