Chromium 40.0.2202.0 (32 and 64 bit) and Chrome 39.0.2171.36 m (32 and 64bit) are not affected by Mactype 1.12.1022 anymore
Opened this issue · 3 comments
GoogleCodeExporter commented
I used an older version of Chromium 64bit and the Mactype rendering was
enabled. It was also enabled in Chrome, also an older version. For other
reasons I decided to update Chromium 64bit to the newest version. After
updating the text lost its Mactype rendering. I checked in the older version of
Chrome and it was disabled there too. Now I've updated both Chromium and
Chrome, both 32 and 64bit and I've reinstalled Mactype but the font rendering
is gone. It's still present in my Windows install, I checked every browser I
have and they all lack the rendering now.
Original issue reported on code.google.com by mirelmir...@gmail.com
on 2 Nov 2014 at 10:51
GoogleCodeExporter commented
Was googling for days and right after posting this question I found the
solution: #enable-direct-write
Original comment by mirelmir...@gmail.com
on 2 Nov 2014 at 10:53
GoogleCodeExporter commented
DirectWrite is the best font rendering that we have available anyways for
Chrome, so just use that. There's no need to even use MacType any more when it
comes to Chrome due to the fact that they enabled it. It also will be much
glitchier and slower with MacType in comparison to the thoroughly-tested
implementation by the Chromium developers.
Original comment by xxCoolOp...@gmail.com
on 6 Nov 2014 at 9:30
GoogleCodeExporter commented
I updated and now it's shitty for some parts of a webpage. For example the chat
screen in Facebook or the content text in ukf.com. Disabled and re-enabled
directwrite and nothing. Btw, without Mactype nothing happens with text in
Chromium. With or without directwrite enabled..
Original comment by mirelmir...@gmail.com
on 25 Nov 2014 at 7:47