Font fallback not working when run with --no-sandbox option
Reported by
kevinsaw...@gmail.com,
Oct 4 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Steps to reproduce the problem: 1. Download https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/fast/text/font-fallback-win.html to a local file 2. Launch Chrome with --no-sandbox option 3. Open downloaded font-fallback-win.html in Chrome window What is the expected behavior? All Characters render What went wrong? Some characters show as box character Did this work before? No Chrome version: 53.0.2785.116 Channel: stable OS Version: 10 Flash Version: Shockwave Flash 23.0 r0
,
Oct 5 2016
https://jsfiddle.net/3cnmnq4w/ This is likely due to the right font fallback interfaces not being propagated to Blink/Skia when the font proxy initialization is skipped. While that could be fixed by getting the interfaces directly from DWrite, there's also no reason to not use the proxy when not using the sandbox, so we should just do that. Also, note that running with the --no-sandbox flag is not secure and should be avoided whenever possible.
,
Oct 6 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8ae5d7f0001e8c138f2468450e3091216e0c35c3 commit 8ae5d7f0001e8c138f2468450e3091216e0c35c3 Author: kulshin <kulshin@chromium.org> Date: Thu Oct 06 18:35:32 2016 Initialize the font proxy even when not using the sandbox Now that we removed the font cache, there is no reason for the font proxy to be tied to sandbox initialization. BUG= 652898 Review-Url: https://codereview.chromium.org/2387373003 Cr-Commit-Position: refs/heads/master@{#423599} [modify] https://crrev.com/8ae5d7f0001e8c138f2468450e3091216e0c35c3/content/renderer/renderer_main_platform_delegate_win.cc
,
Oct 6 2016
,
Oct 27 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8ae5d7f0001e8c138f2468450e3091216e0c35c3 commit 8ae5d7f0001e8c138f2468450e3091216e0c35c3 Author: kulshin <kulshin@chromium.org> Date: Thu Oct 06 18:35:32 2016 Initialize the font proxy even when not using the sandbox Now that we removed the font cache, there is no reason for the font proxy to be tied to sandbox initialization. BUG= 652898 Review-Url: https://codereview.chromium.org/2387373003 Cr-Commit-Position: refs/heads/master@{#423599} [modify] https://crrev.com/8ae5d7f0001e8c138f2468450e3091216e0c35c3/content/renderer/renderer_main_platform_delegate_win.cc
,
Nov 4 2016
[Automated comment] removing mislabelled merge-merged-2840
,
Jan 2 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kulshin@chromium.org
, Oct 4 2016Owner: kulshin@chromium.org
Status: Assigned (was: Unconfirmed)