Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348234

Summary: [CellEditors] TextCellEditor doesn't explicitly inherit parent's foreground color
Product: [Eclipse Project] Platform Reporter: Chris Williams <chris.a.williams>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: prakash
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Chris Williams CLA 2011-06-03 11:51:13 EDT 
Build Identifier: I20110428-0848

We specifically force different fg and bg colors on various views as part of a user preference. For the Variables view we've set a black background and white foreground color. If the user edits a variable value, the fg of that cell becomes black, so it's black on black and is unreadable.

if you look at TextCellEditor, lines 189-190, it's explicitly setting font and bg to the parent's. I had to add a Tree Paint event listener for windows that grabbed the TreeViewer's cell editors, iterated over them and called getControl().setForeground() to force our foreground color.

Reproducible: Always

Steps to Reproduce:
1. Listen for opening of Variables view.
2. Set the fg to white and bg to black on the tree of the Variables view.
3. Run a debug session, hit a breakpoint.
4. Select a variable's value cell to edit it, click again to make sure you're editing and don't just have the value selected, the fg should now be black and the background is black too.
Comment 1 Lars Vogel CLA 2019-11-14 02:18:39 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.