when the system font has some problem,chromium browser cannot show page normally
Reported by
guyouyou...@gmail.com,
Apr 11 2016
|
||||
Issue description
Chrome Version : 49.0.2623.105(android)
URLs (if applicable) :No
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:don't know
Firefox:don't know
IE:don't know
What steps will reproduce the problem?
(1)adb push error.ttf /system/fonts/hwbold.ttf
(2)adb shell stop
(3)adb shell start
What is the expected result?
when i open a page ,it can show normally.
What happens instead?
But the browser show me the render progress carshed
Please provide any additional information below. Attach a screenshot if
possible.
in chromium 37 .it can show normally,after chromium 38 it carshed
i think it could be skia problem.
maybe blew two patched effect this:
https://chromium.googlesource.com/skia/+/94fa4b99e2a53e997a90c7808cc5263f1bf40c9f%5E%21/#F0
https://chromium.googlesource.com/skia/+/8e69676bf559b9f3105f9107136ec93dfb124e80
,
Apr 13 2016
,
Apr 14 2016
,
Apr 14 2016
Adding djsollen@ and bungeman@ for confirmation, but it's not clear why we'd want to support this behavior. Your 'error.ttf' file appears to be invalid; ttfdump can't parse it, the header bytes don't look right for a TTF, and the unix 'file' command doesn't recognize it as any sort of known valid file.
,
Apr 15 2016
i know what's the problem. It's this change caused this problem. https://chromium.googlesource.com/skia/+/94fa4b99e2a53e997a90c7808cc5263f1bf40c9f%5E%21/#F0 Because we cannot found family "arial",so the skia returns error (NULL) So the browser cannot render normally. We can just add this family to /system/etc/fonts.xml .it could solve this problem.
,
Apr 15 2016
>>>Adding djsollen@ and bungeman@ for confirmation, but it's not clear why we'd want >>>to support this behavior. >>>Your 'error.ttf' file appears to be invalid; ttfdump can't parse it, the header >>>bytes don't look right for a TTF, and the unix 'file' command doesn't recognize it >>>as any sort of known valid file. if we download error ttf or ttf parse error,can produce this problem. I think we should do some thing to prevent browser to crashed
,
Apr 15 2016
I agree with Tom's assessment that this is a WontFix issue. The font files you are replacing are in /system/fonts which is on a read only partition of the device. You have to have root access your phone to have modify those files. Further, I'm not sure what your comments about arial are about as "arial" has been a valid font family for Android apps as long as I can remember. https://android.googlesource.com/platform/frameworks/base/+/master/data/fonts/ |
||||
►
Sign in to add a comment |
||||
Comment 1 by guyouyou...@gmail.com
, Apr 11 2016