<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [GTK] WebProcess crashes when quickly attempting many DnD operations"
href="https://bugs.webkit.org/show_bug.cgi?id=138468#c43">Comment # 43</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [GTK] WebProcess crashes when quickly attempting many DnD operations"
href="https://bugs.webkit.org/show_bug.cgi?id=138468">bug 138468</a>
from <span class="vcard"><a class="email" href="mailto:darin@apple.com" title="Darin Adler <darin@apple.com>"> <span class="fn">Darin Adler</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=138468#c42">comment #42</a>)
<span class="quote">> FWIW, js-test-pre.js will create the console element if there isn't one in
> markup. It is sometimes useful to have an explicit one in test source to
> guarantee its position in the DOM tree, which may be the case here.</span >
To put this in a larger context, tests using js-test-pre.js are often written in ways that are needlessly complex, for example with the test JavaScript put in a separate file (valuable for pure JavaScript tests that can be run without involving HTML, but not a good practice for the other tests), or with explicit elements like the console that are only needed in certain special cases, not for all tests.
When writing new tests we want to avoid repeating these old patterns unnecessarily.</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>