<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 - MemoryPressureHandler shouldn't know how to release WebCore memory"
href="https://bugs.webkit.org/show_bug.cgi?id=160497#c35">Comment # 35</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - MemoryPressureHandler shouldn't know how to release WebCore memory"
href="https://bugs.webkit.org/show_bug.cgi?id=160497">bug 160497</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=160497#c34">comment #34</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=160497#c31">comment #31</a>)
> > Safari uses both legacy WebKit (WebKit1) and modern WebKit (WebKit2). Some
> > day it might get to the point where it has no dependency on legacy WebKit,
> > but at the moment it still uses both.
>
> Anywhere I can learn about why Safari still needs legacy WebKit and what it
> uses it for? That's really surprising to me and I'm curious!</span >
I don’t think there is anywhere to learn that, but I am willing to disclose a little bit: At some point in the recent past, there was some use of legacy WebKit in some of the Safari Browser Extension support.
Also, keep in mind that WebKit is a system framework on macOS; Safari can invoke some other macOS framework and nothing prevents that framework from using some bit of WebKit API for some task.</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>