| Issue 7758: | GDI++ can't rander Chrome font display in full function mode | |
| 7 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Chrome Version : 2.0.162.0
URLs (if applicable) : All pages
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 3: N/A
Firefox 3: OK
IE 7: OK
What steps will reproduce the problem?
1. Close ClearType in Windows, and launch GDI++ render engine;
2. Launch Chrome without any parameter and open a page;
3. All fonts in Chrome are not rendered as GDI++ is enabled;
4. Close Chrome;
5. Turning off the sandbox mode by edit the properties of the shortcut of
Chrome. Using --no-sandbox parameter to launch Chrome;
6. Launch Chrome and open a page again;
7. GDI++ will works now.
What is the expected result?
GDI++ works with turn on sandbox mode.
What happens instead?
Fonts in Chrome are not rendered as expected as GDI++ enabled.
Please provide any additional information below. Attach a screenshot if
possible.
GDI++ is a rastering model built atop GDI+ by an independent developer
(name uncertain) from Japan. It makes fonts on desktop to be bolder, close
to the way that MacOS renders them.
|
|||||||||||||||||||||
,
Feb 17, 2009
(No comment was entered for this change.)
Status: Duplicate
Owner: all-bugs...@chromium.org Cc: js...@chromium.org anan...@chromium.org hb...@chromium.org Mergedinto: 3478 |
||||||||||||||||||||||
,
May 15, 2009
Launching Google Chrome with the "--no-sandbox" parameter allowed GDI++ font rendering to work successfully. My only concern is what this parameter is actually doing to the browser. |
||||||||||||||||||||||
,
May 16, 2009
Yes, use --no-sandbox will allow GDI++ to work, but this will cause security issue, so it is not recommended. I wish Google can implements font smooth in Chrome itself, user can change it in preference settings just as in Safari. |
||||||||||||||||||||||
 Sign in to add a comment
|
||||||||||||||||||||||
