Bug 312696 - [preferences][syntax highlighting] Create a mechanism to determine the config settings affecting the appearance of a given piece of text
Summary: [preferences][syntax highlighting] Create a mechanism to determine the config...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.5.2   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-12 15:28 EDT by Brad Davis CLA
Modified: 2019-09-06 15:33 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brad Davis CLA 2010-05-12 15:28:54 EDT
Build Identifier: M20100211-1343

When customizing my eclipse UI to display text with a dark background and light foreground text, I constantly run across situations where I can't find the setting to configure a particular kind of background or foreground color.  For instance, currently the background for 'matched search terms' is offwhite and the forground text I'm search for is teal, meaning matched search items are nearly unreadable.  It would be very helpful if I could select an item from the eclipse menu and then click on a piece of text and have eclipse determine where the foreground and background color for that piece of text were configured and take me there.  Alternatively, a context menu option to directly set the text color would work as well.

Reproducible: Always

Steps to Reproduce:
1. Set the color scheme to use a dark background color and light foreground color.
2. Search for an item
3. See the matched search results are nearly unreadable.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:33:13 EDT
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.