<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Option+Click not jumping to resource"
href="https://bugs.webkit.org/show_bug.cgi?id=146498#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Option+Click not jumping to resource"
href="https://bugs.webkit.org/show_bug.cgi?id=146498">bug 146498</a>
from <span class="vcard"><a class="email" href="mailto:joepeck@webkit.org" title="Joseph Pecoraro <joepeck@webkit.org>"> <span class="fn">Joseph Pecoraro</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=146498#c3">comment #3</a>)
<span class="quote">> Comment on <span class=""><a href="attachment.cgi?id=256271&action=diff" name="attach_256271" title="Patch">attachment 256271</a> <a href="attachment.cgi?id=256271&action=edit" title="Patch">[details]</a></span>
> Patch
>
> The force tab stuff was added because I was seeing tab switches during
> cookie restore. Maybe we don't need it now because cookie restore is only
> done when the tab is selected?</span >
That was exactly what I was thinking and why I suggested this approach to Devin. I cannot think of any case where we don't want to switch to a relevant tab when trying to show a new content view. The idea with window.event was clever, but I can't think of cases where we would trigger switching content views that wasn't somehow user gesture triggered. Even if we end up needing to keep/restore this parameter, I'd rather see it negated, and have the default behavior allow for switching tabs.</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>