New issue
Advanced search Search tips

Issue 688608 link

Starred by 2 users
Status: WontFix
Owner:
drott@chromium.org
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

document.fonts.ready promise fires too early

Project Member Reported by drott@chromium.org, Feb 4 2017 
The document.fonts.ready promise seems to fire too early, causing the tests for font style matching to fail or be flaky, compare  issue 515454 .

The problem seems to be that the promise resolves when the fonts have downloaded, but before layout with the new font has completed. 

haraken@ suggests that we should look for where the call is made for PromiseResolver to resolve the promise and postpone that until after layout for the newly arrived fonts has completed.
Project Member

Comment 1 by sheriffbot@chromium.org, Feb 12 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by e...@chromium.org, Feb 12 2018

Cc: drott@chromium.org
Is this still an issue? If so do we have a test case or demonstration of the problem?

Comment 3 by e...@chromium.org, Feb 13 2018

Cc: -drott@chromium.org
Owner: drott@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by drott@chromium.org, Feb 19 2018

Status: WontFix (was: Assigned)
As the tests in  issue 515454  per comment in https://bugs.chromium.org/p/chromium/issues/detail?id=515454#c6 do no longer appear flaky, we don't have a reproduction anymore. I checked the dashboard and the tests have now moved to inspector style .js tests, which also appear stable. Closing as WontFix.
►

Sign in to add a comment