DocumentLoader should think it's loading while the parser is still active
Created attachment 189410 [details] Mostly for the EWSes to munch on.
Comment on attachment 189410 [details] Mostly for the EWSes to munch on. Attachment 189410 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/16646691 New failing tests: http/tests/security/feed-urls-from-remote.html
Looking at the failure now.
Reduction of the hang: reduction.html: <script> testRunner.dumpAsText(); testRunner.waitUntilDone(); </script> <iframe src="feed.html" onLoad="testRunner.notifyDone()"></iframe> feed.html: <a id="myFeed">The feed:// URL</a> <script> var myFeed = document.getElementById("myFeed"); myFeed.href = "feed://127.0.0.1:" + document.location.port + "/security/resources/feed.xml"; var evt = document.createEvent("MouseEvents"); evt.initMouseEvent("click", true, true, window, 0, 0, 0, 0, 0, false, false, false, false, 0, null); myFeed.dispatchEvent(evt); </script> feed.xml: <empty> (can be anything)
I'm not sure if the feed: part is important. But a data url seemed to not cause the hang, and invalid urls also failed to hang.
Actually, that reduction times out even w/o my change. However, adding back the setCustomPolicyDelegate calls, makes it complete again!
So at first glance, this change seems to change behavior of the policyDelegate codepath in the loader, causing this one test which depended on this to fail. :) It's not clear yet if this is just a bug in Chromium's DRT, relating to this quirk in the policyDelgate codepath, or if this could be a real bug for the policyDelegate codepath (which would only affect Mac). Building Mac now.
More context: main.html: <script> testRunner.dumpAsText(); testRunner.waitUntilDone(); </script> <iframe src="resource.html" onLoad="testRunner.notifyDone()"></iframe> resource.html: <script> location.href = "feed://127.0.0.1:" + document.location.port + "/security/resources/feed.xml"; </script> Hangs Chromium DRT, but does not hang Mac (w/o the patch). Changing feed: to http: does not hang Chromium DRT (with or w/o the patch!)
Comment on attachment 189410 [details] Mostly for the EWSes to munch on. I'm going to complete this in bug 109995 and leave this for solving the chromium DRT oddity (if we ever chose to). Most of the other tests in this directory are already marked Wontfix it seems.
bug 109995 also broke Mac WK1, seen in bug 110554.