search

fatground / mactype

Automatically exported from code.google.com/p/mactype
0 stars 0 forks source link

Websites 'broken' after loading on Chrome #1

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Open Google Chrome
2. Open a website (I tried with http://facebook.com/ and http://alt1040.com/)

What is the expected output? What do you see instead?
I try to navigate on some sites and it loads but when load is complete, it 
shows the error screen (aw snap! dark blue screen)

What version of the product are you using? On what operating system?
Chrome 18.0.1025.152 m on Windows 7 64 bit

Please provide any additional information below.
It only happens with some sites. I think it is a mactype issue because when I 
disable mactype, websites load normally.

Original issue reported on code.google.com by jesus...@gmail.com on 11 Apr 2012 at 3:08

GoogleCodeExporter commented 8 years ago 
everything seems to be fine on my system. Did you installed any suspicious 
extension that may conflict with mactype?

Original comment by flyingsn...@gmail.com on 12 Apr 2012 at 1:30

GoogleCodeExporter commented 8 years ago 
Both of those mentioned sites work fine here, too.

Original comment by Elev...@gmail.com on 14 Apr 2012 at 8:30

GoogleCodeExporter commented 8 years ago 
I have the same problem. It happen when there is a facebook module in the 
webpage.
Sorry for my english, i'm french

Original comment by gwenael....@gmail.com on 12 Jun 2012 at 11:32

GoogleCodeExporter commented 8 years ago 
My Chrome usually crash several times a day. When I disable the mactype, the 
crash won't happy again.

Original comment by netcof...@gmail.com on 3 Jul 2012 at 3:18

GoogleCodeExporter commented 8 years ago 
So, how do we disable mactype from working on the Chrome process?

Original comment by chunkych...@gmail.com on 8 Aug 2012 at 8:22

GoogleCodeExporter commented 8 years ago 
I got the same issue. Facebook is not OK. Neither are some websites or pages.
Didn't tried to solve it yet, but it's interesting if it can be disabled.

At the time of GDI++, Chrome behaved stangely too but in a different manner 
(font rendering). Adding chrome.exe in a list of exclusions fixed the case :

I quote : "Workaround worked for me. Edit C:\Program 
Files(x86)\gdipp_setting.xml and add a line 

<process>chrome\.exe</process> 

in the <exclude> section to disable gdipp. Then reboot or Run services.msc, 
find the 32 and 64 bit instances of gdipp and restart each one."

Original comment by vincedch...@gmail.com on 15 Sep 2012 at 7:36

GoogleCodeExporter commented 8 years ago 
Confirmed not working in Chrome 22.0.1229.79.

Original comment by Elev...@gmail.com on 28 Sep 2012 at 5:42

GoogleCodeExporter commented 8 years ago 
The latest version of MacType has corrected this issue! :D

Original comment by Elev...@gmail.com on 28 Oct 2012 at 5:19

GoogleCodeExporter commented 8 years ago 
Is this what were calling fixed? 
https://www.dropbox.com/s/cr8zqa9um3atpf5/Screenshot%20%2813%29.png

Original comment by danieldi...@gmail.com on 4 Jan 2013 at 6:25

GoogleCodeExporter commented 8 years ago 
#9: MacType just enables ClearType on installation.  It's probably better than 
no smoothing at all, but is obviously not a proper solution for the lack of 
font smoothing in Chrome.

Original comment by jmbat...@gmail.com on 31 Jan 2013 at 4:12

GoogleCodeExporter commented 8 years ago 
this a generally because Chrome can benefit from mactype only if cleartype is 
on, or it will use its build-in font engine to render.

font smoothing is definitely working in Chrome if cleartype is turned on. 
however, the effect is quite different from other applications because chrome 
has an internal process of font rendering. therefore, there is no way you can 
solve the problem.

Original comment by flyingsn...@gmail.com on 3 Feb 2013 at 7:10

GoogleCodeExporter commented 8 years ago 
The issue is still happening on Chrome Version 28.0.1500.72 m. And for me, it 
is only on Facebook.com.

It maybe due to plugins, because at work, I have no problem with Chrome and 
Mactype.

By the way, can we have a Mactype error log so that whenever something 
happened, we can look at that log first ?

Original comment by phungkim...@gmail.com on 17 Jul 2013 at 6:22