Trigger font scanning at browser startup, not lazily on demand
Since font scanning is now an asynchronous, BEST_EFFORT priority task, we should trigger it at startup so it may already be ready when a renderer requests it. Previously, it was a synchronous task, triggered by when a renderer requested the lookup table for the first time. Triggering it at startup matches the approach we take on Windows 7 and 8. Bug: 973394 Change-Id: I2e890058c538ed157217e98d1f4a0bdba639a602 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1681760Reviewed-by:Avi Drissman <avi@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#673386}
Showing
Please register or sign in to comment