<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - New force-related DOM events should fire in WK1 views"
href="https://bugs.webkit.org/show_bug.cgi?id=144663#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - New force-related DOM events should fire in WK1 views"
href="https://bugs.webkit.org/show_bug.cgi?id=144663">bug 144663</a>
from <span class="vcard"><a class="email" href="mailto:thorton@apple.com" title="Tim Horton <thorton@apple.com>"> <span class="fn">Tim Horton</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=144663#c6">comment #6</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=144663#c5">comment #5</a>)
> > > Source/WebKit/mac/WebView/WebHTMLView.mm:-3844
> > > - [[[self _webView] _immediateActionController] webView:[self _webView] willHandleMouseDown:event];
> >
> > Whaaaaaa?
> >
>
> This is because mouseDown used to come after the immediate action! Remember?
> We used to have shenanigans like this in WK2 as well, and we were able to
> remove them when we switched to delaysPrimaryMouseEvents:NO. This code was
> there purely because we were getting mouse down at a weird time.</span >
Righto.
<span class="quote">> > Could you not keep this in EventHandler instead and avoid keeping it here?
>
> Hmmmmmmm. I'll have to think this over. This is a closer mirror to what we
> do in WK2. If we moved it to EventHandler, we would have WK1 only member
> variables there, which we actually manage to avoid at this point.</span >
Could you not then perhaps use them for WK2 as well, and share some code that you currently have duplicated between WebView and WKView?</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>