<html>
<head>
<base href="https://bugs.webkit.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add a warning for unused link preloads."
href="https://bugs.webkit.org/show_bug.cgi?id=165670#c30">Comment # 30</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Add a warning for unused link preloads."
href="https://bugs.webkit.org/show_bug.cgi?id=165670">bug 165670</a>
from <span class="vcard"><a class="email" href="mailto:youennf@gmail.com" title="youenn fablet <youennf@gmail.com>"> <span class="fn">youenn fablet</span></a>
</span></b>
<pre>(In reply to Alex Christensen from <a href="show_bug.cgi?id=165670#c29">comment #29</a>)
<span class="quote">> I don't know much about DumpJSConsoleLogInStdErr, but I think it would be
> cleaner to add something to TestRunner.idl or Internals.idl to disable the
> logs from within the test rather than having to know about this magic value
> in TestExpectations to figure out what is going on.</span >
DumpJSConsoleLogInStdErr is mostly for imported W3C tests.
In most cases, if you can tweak the test, you can fix the flakiness issues, which makes TestRunner method not necessary, although we can add it for convenience.
If we were able to inject WebKit specific scripts on imported W3C tests without modifying them (like testXX.webkit.js file next to textXX.js), we could probably get rid of DumpJSConsoleLogInStdErr and use TestRunner.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>