Clean up font loading

third_party/WebKit/LayoutTests/http/tests/webfont/css-change-in-swap-period.html

Index: third_party/WebKit/LayoutTests/http/tests/webfont/css-change-in-swap-period.html
diff --git a/third_party/WebKit/LayoutTests/http/tests/webfont/css-change-in-swap-period.html b/third_party/WebKit/LayoutTests/http/tests/webfont/css-change-in-swap-period.html
index ea00bc20b148fe5195f38eb84d09b4492ff47e1e..c1c13e38e9c1bcef7529587ff1c356be937a7149 100644
--- a/third_party/WebKit/LayoutTests/http/tests/webfont/css-change-in-swap-period.html
+++ b/third_party/WebKit/LayoutTests/http/tests/webfont/css-change-in-swap-period.html
@@ -18,7 +18,9 @@
 if (window.testRunner)
     testRunner.waitUntilDone();
 
-window.onload = function() {
+window.onload = setTimeout(runTest, 0);

[Nate Chapin, 2016/04/07 23:46:16]

Without the setTimeout(,0), the font load would start synchronously and block
test completion for the full delay=8000, leading to timeouts.

The change that lead to the font load blocking test completion isn't a concern
in the real world, because the bit that the test harness is checking
(WebLocalFrameImpl::isResourceLoadInProgress) is only used for determining test
completion. It doesn't block things like the parent frame's load event or
didStopLoading() callbacks.

[hiroshige, 2016/04/08 01:02:04]

Shouldn't this be |window.onload = function() { setTimeout(runTest, 0); };| ?

[Nate Chapin, 2016/04/11 18:47:32]

Wow, I'm bad at Javascript. Done.

+
+function runTest() {
     document.getElementById('test').classList.add('test');
     setTimeout(function() {
         var newStyle = document.createElement('style');