Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 509538 - [Dark Theme] Java Sort Order preference is not properly styled
Summary: [Dark Theme] Java Sort Order preference is not properly styled
Status: CLOSED DUPLICATE of bug 501800
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Patrik Suzzi CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-20 11:24 EST by Patrik Suzzi CLA
Modified: 2022-01-27 03:46 EST (History)
2 users (show)

See Also:

Attachments
Image: error on preferences. (43.00 KB, image/png)
2016-12-20 11:24 EST, Patrik Suzzi CLA 		no flags Details
Animation of the issue, plus SWT Spy and CSS Spy (953.25 KB, image/gif)
2016-12-20 11:25 EST, Patrik Suzzi CLA 		no flags Details
DarkTheme_Java_Appearance_MemberSortOrder (35.79 KB, image/png)
2022-01-27 03:44 EST, Niraj Modi CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Patrik Suzzi CLA 2016-12-20 11:24:04 EST 
Created attachment 265982 [details]
Image: error on preferences.

In preferences : Java > Appearance > Java Sort Order, the sort member table is not styled correctly when is de-selected.
Comment 1 Patrik Suzzi CLA 2016-12-20 11:25:46 EST 
Created attachment 265983 [details]
Animation of the issue, plus SWT Spy and CSS Spy

Note: the issue happens only on windows and not in Linux
Comment 2 Patrik Suzzi CLA 2016-12-20 11:46:37 EST 
This could be linked to Bug 501800.
Comment 3 Niraj Modi CLA 2022-01-27 03:44:16 EST 
Created attachment 287909 [details]
DarkTheme_Java_Appearance_MemberSortOrder

No longer an issue with Darktheme anymore on Windows10.
Comment 4 Niraj Modi CLA 2022-01-27 03:46:37 EST 
(In reply to Patrik Suzzi from comment #2)
> This could be linked to Bug 501800.

Not 100% sure.. but looks duplicate of bug 501800, hence closing.

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