New issue
Advanced search Search tips

Issue 674359 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Scroll Anchoring: mitigation failure with web fonts

Project Member Reported by kenjibaheux@chromium.org, Dec 15 2016

Issue description

What steps will reproduce the problem?
1. Go to https://www.zachleat.com/web-fonts/scroll-anchoring/ on a mobile device
2. The fallback font will be used after 3s
3. The web font will be available and used after 10s 

"Wait for the web font to timeout (3 seconds) rendering the fallback font. The web font will render after a 10 second timeout, which reflows and changes your scroll position."

What is the expected result?
4. Scroll Anchoring is able to mitigate the reflow triggered when the web font is used.


What happens instead of that?
4. Scroll Anchoring is not able to mitigate the reflow triggered when the web font is used.


Not quite sure this still is an issue on the latest canary.



 
Status: Untriaged (was: Unconfirmed)
I was able to reproduce this on Google Chrome	57.0.2951.0 (Official Build) canary (64-bit) with DevTools' responsive mode (default settings).

When the web font is used, the first header takes more space and uses 2 lines (depends on the viewport size, I guess) which triggers a reflow but is not mitigated by SA.

Comment 2 by bokan@chromium.org, Dec 15 2016

I can repro on Android Chrome Beta 55.0.2883.77. Can't repro on Canary/Dev but the font when I try it in canary/dev doesn't change so that's probably why.

Comment 3 by skobes@chromium.org, Dec 15 2016

Status: Fixed (was: Untriaged)
This was fixed by r427584 (M56), which removed "font-face" from the set of SANACLAP triggers.

Re #2: You may need to clear the cache to see the font change.

Sign in to add a comment