<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 - Look up will deepend every time."
href="https://bugs.webkit.org/show_bug.cgi?id=144101#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Look up will deepend every time."
href="https://bugs.webkit.org/show_bug.cgi?id=144101">bug 144101</a>
from <span class="vcard"><a class="email" href="mailto:jimoase@mac.com" title="Jim Oase <jimoase@mac.com>"> <span class="fn">Jim Oase</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=144101#c11">comment #11</a>)
<span class="quote">> WebKit nightlies are indeed unusual, because they use Safari that is
> installed on your system. This is an integral part of how nighlties work, so
> as Tim said, this is a bug in OS X 10.10.3 that needs to be reported to
> Apple.
>
> Thank you for following up!</span >
In another life I had programmers tell me their code was good so its got to be something else causing the problem. My approach was to ask for a walk through of the code with a couple more people sitting in.
An amazing number of times, during the presentation, the programmer would stop, make an amazement statement and the problem was found.
So the premise is that when Safari and all other applications do the lookup routines they accesses OS X is a different way than WebKit even though Safari and WebKit use the same routines?
What is the problem that causes OSX to recognize and treat WebKit different?
Does OSX know it's WebKit calling via Safari routines?
What changed between the build that worked and the first one that didn't work? Did OSX get an upgrade? I will look back at builds and find when the change occurred. If there is such an occurrence than OSX is not the problem.</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>