I think it's font related, mostly about fallbacks. Wonder if it's faster on a JP locale device 
-
-
Here's the tracefile from a Nokia 2:https://www.dropbox.com/s/0jfnylpbe1mng29/trace_Nokia_2_yamaha_lightweight_site.json.gz?dl=0 …
1 reply 0 retweets 0 likes -
The little green tasks within this layotu are those `FontCache::FallbackFontForCharacter` tasks, which I assume do some sort of I/O:pic.twitter.com/GwuNYdqjX9
1 reply 0 retweets 0 likes -
Any ideas,
@eae?1 reply 0 retweets 0 likes -
Replying to @slightlylate @kosamari and
My guess (bc I want the answer and I’m baiting
@eae with a likely incorrect one) is that it does the whole blink-harfbuzz-skia dance for every char and needs to fallback through bad serifs until it gets to one with the glyph, but the OS arial/helvetica should have it so
1 reply 0 retweets 2 likes -
Replying to @notwaldorf @slightlylate and
Pretty close, you've been paying attention
@notwaldorf, I'm impressed!2 replies 0 retweets 2 likes -
Replying to @eae @notwaldorf and
Font fallback in Chrome works by trying to shape with the first specified font-family then falling back to subsequent ones for each run of glyphs where the first one did not have sufficient coverage.
1 reply 0 retweets 6 likes -
Replying to @eae @notwaldorf and
In cases where none of the specified fonts have coverage we query the OS for an appropriate font for the first glyph in the "unshaped" sequence and shape as much of the remainder with that.
1 reply 0 retweets 2 likes -
Replying to @eae @notwaldorf and
The behavior of the yamaha-motor site is pretty typical in that none of the specified fonts have coverage for Japanese characters, but has coverage for the space character, triggering OS level fallback for each "word".
1 reply 0 retweets 2 likes -
Replying to @eae @notwaldorf and
The way to fix this is to either specify a font-family that has full coverage for Japanese, or to not specify a font at all, triggering a locale specific default.
1 reply 0 retweets 1 like
Is there a way to diagnose this pathology in devtools?
/cc @hashseed @paul_irish
-
-
Replying to @slightlylate @notwaldorf and
Yes and it's really easy. The devtools team has done a fantastic job surfacing font-related issues over the last few years. Inspect the element with the text content and check then "Rendered Fonts" section of the "Computed" styles tab. Ideally this should list a single font.
2 replies 0 retweets 2 likes -
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.