Bug 1337401 - Underscores are not always displayed in eclipse when scaling factor of fonts is modified in gnome-tweak
Summary: Underscores are not always displayed in eclipse when scaling factor of fonts ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alexander Kurtakov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-19 06:45 UTC by Guillaume Bernard
Modified: 2016-07-29 13:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-29 13:45:45 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Screenshot of the bug (8.05 KB, image/png)
2016-05-19 06:45 UTC, Guillaume Bernard 		no flags Details
View All

Description Guillaume Bernard 2016-05-19 06:45:24 UTC 
Created attachment 1159257 [details]
Screenshot of the bug

Description of problem:
When the value of the scaling factor of fonts is modified (via gnome-tweak), underscores are not always displayed in eclipse.

Version-Release number of selected component (if applicable):
4.6.0-0.6.git201605092000.fc24

How reproducible:
Depending of the scrolling position, some underscores are sometimes displayed.

Steps to Reproduce:
1. Open gnome-tweak
2. Go to "fonts" tab and set scaling factor to 1.15
3. Open a file containing underscores in eclipse.

Actual results:
Some underscores are displayed but most of them are not.

Expected results:
All underscores should be visible.

Additional info:
There was no bug in previous version of eclipse (mars).
Comment 1 Guillaume Bernard 2016-07-29 13:39:45 UTC 
It seems to be solved by a recent update.
Comment 2 Alexander Kurtakov 2016-07-29 13:45:45 UTC 
(In reply to Guillaume Bernard from comment #1)
> It seems to be solved by a recent update.

I love self-fixing bugs. Closing.
Note You need to log in before you can comment on or make changes to this bug.