Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome 37.0.2062.102 m problem #120

Open
GoogleCodeExporter opened this issue Aug 7, 2015 · 11 comments
Open

Chrome 37.0.2062.102 m problem #120

GoogleCodeExporter opened this issue Aug 7, 2015 · 11 comments

Comments

@GoogleCodeExporter
Copy link
Contributor

What steps will reproduce the problem?
1. Running latest version (37.0.2062.102) Google Chrome browser
2.
3.

What is the expected output? What do you see instead?
The font has become very sharp and painful for eyes and lost it's 
enough-minimum boldness.

What version of the product are you using? On what operating system?
Chrome 37.0.2062.102 m, Windows 7 x86, the latest version of MacType

Please provide any additional information below.
First of all, you, guys, did a great job! This deeply changed my whole working 
experience. 
I've been using MacType (as a Tray Application) about 5 months and it worked 
like a charm for all my Windows apps, including Google Chrome. But a couple of 
days ago MacTray stopped rendering fonts from Chrome. The fonts became sharp. 
All other apps are ok. 

Original issue reported on code.google.com by [email protected] on 29 Aug 2014 at 9:15

@GoogleCodeExporter
Copy link
Contributor Author

I've just tried to use the portable version of old Google Chrome 27 and MacType 
works well there. I guess the problem is in the current version of Google 
Chrome. Could you actualize your software for the latest versions of Chrome? 

Original comment by [email protected] on 29 Aug 2014 at 9:18

@GoogleCodeExporter
Copy link
Contributor Author

Screenshot of current font 

Original comment by [email protected] on 29 Aug 2014 at 9:37

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

ENABLE #disable-direct-write FLAG helped! ISSUE RESOLVED!

Original comment by [email protected] on 29 Aug 2014 at 10:08

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

The same problem seems to be happening again. Now with chrome version 
37.0.2062.124 m.
Disabling Direct write doesn't fix it for me anymore.

Original comment by [email protected] on 30 Sep 2014 at 3:53

@GoogleCodeExporter
Copy link
Contributor Author

[deleted comment]

@GoogleCodeExporter
Copy link
Contributor Author

I've just checked my Google Chrome version: 
"Version 37.0.2062.124 m
Google Chrome is up to date."

Notice that I'm using a Registry Mode of MacType now and I have no problems. 

Perhaps, you should try playing with that flag I showed. I would have tried 
something like this: 
- enable flag => restart browser => check what happens.
then
- disable flag => restart browser => check what happens.

If this will not work, you can also try looking through the list of other flags 
and search for possible flags related with "fonts". I'm not sure, but, perhaps, 
there's some flag that blocks MacType. 

Original comment by [email protected] on 30 Sep 2014 at 8:30

@GoogleCodeExporter
Copy link
Contributor Author

Hi!

It got back to normal, my eyes are not hurting or bleeding anymore.
Chrome is still at Version 37.0.2062.124 m, and Disable DirectWrite is enabled 
(as it was before the problem appeared).
All MacType Chrome processes are "Running".

The problem appeared after I updated and relaunched chrome.
It was solved after disabling and enabling again the flag, restarting chrome, 
restarting everything else which could be interfering with it, and restarting 
the computer.
It was probably the PC restart that solved it though.

Original comment by [email protected] on 1 Oct 2014 at 3:03

@GoogleCodeExporter
Copy link
Contributor Author

It's great to hear that. Congrats!

Original comment by [email protected] on 1 Oct 2014 at 3:10

@GoogleCodeExporter
Copy link
Contributor Author

I believe restarting chrome after disabling direct write is the solution

Original comment by [email protected] on 26 Nov 2014 at 12:01

@GoogleCodeExporter
Copy link
Contributor Author

After update 40, refer here: 
https://code.google.com/p/mactype/issues/detail?id=130&start=100

Original comment by [email protected] on 6 Mar 2015 at 6:16

@GoogleCodeExporter
Copy link
Contributor Author

@alpha, thanks for the reference, it helped!

Original comment by [email protected] on 9 Mar 2015 at 11:44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant