Community
Participate
Working Groups
Created attachment 240799 [details] Screenshot See screenshot.
Andrea, can you look at that?
This should not happen with the workaround provided in my last commits, can you try with it? I see that you've taken the screenshot on ubuntu/linux but you have the lighter gray settings for Form elements in .MPart that, as of last theme update, should be applied only on Windows (on Windows eg. checkboxes and radio labels are forced to a native black font that cannot be seen easily with darker Form background). There is anyway a bug in the CSS engine when it paints the widgets in active/focused Form: styles are not applied/painted until the user focus or unfocus the active Part for the first time (Form background and FormHeading background/color are white as in the default theme and then become dark on the first focus/unfocus, it happens for any Form in any tab).
(In reply to Andrea Guarinoni from comment #2) > This should not happen with the workaround provided in my last commits, can > you try with it? > I see that you've taken the screenshot on ubuntu/linux but you have the > lighter gray settings for Form elements in .MPart that, as of last theme > update, should be applied only on Windows (on Windows eg. checkboxes and > radio labels are forced to a native black font that cannot be seen easily > with darker Form background). I try with the new version and update the bug. Thanks > There is anyway a bug in the CSS engine when it paints the widgets in > active/focused Form: styles are not applied/painted until the user focus or > unfocus the active Part for the first time (Form background and FormHeading > background/color are white as in the default theme and then become dark on > the first focus/unfocus, it happens for any Form in any tab). Do we have a bug for this already?
(In reply to Lars Vogel from comment #3) > > Do we have a bug for this already? I've just opened it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=430199
Thanks Andrea, the missing styling is indeed based on Bug 430199. Marking as duplicate. *** This bug has been marked as a duplicate of bug 430199 ***