<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:bburg@apple.com" title="Brian Burg <bburg@apple.com>"> <span class="fn">Brian Burg</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Web Inspector: can't navigate back to same view state after option-clicking a CSS property in style sidebar"
href="https://bugs.webkit.org/show_bug.cgi?id=151919">bug 151919</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Web Inspector: can't navigate back to same view state after option-clicking a CSS property in style sidebar"
href="https://bugs.webkit.org/show_bug.cgi?id=151919#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Web Inspector: can't navigate back to same view state after option-clicking a CSS property in style sidebar"
href="https://bugs.webkit.org/show_bug.cgi?id=151919">bug 151919</a>
from <span class="vcard"><a class="email" href="mailto:bburg@apple.com" title="Brian Burg <bburg@apple.com>"> <span class="fn">Brian Burg</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=151919#c4">comment #4</a>)
<span class="quote">> From a UX standpoint. Back buttons in most (all?) apps including Safari
> don't switch containers (tabs). The Elements tab does not have back/forward
> buttons, but would you need to add them there so forward could take you
> "back" to the Resource you just came back from?
>
> The only UI analogous to this idea that I know of would be iOS 9's app back
> button that shows up in the status bar. Which is a different affordance, not
> connected to the content browser back/forward buttons.</span >
I guess it's just a consequence of treating each tab as its own content browser. This makes more sense to me in Safari than in Web Inspector, since our content views have lots of entangled state (most notably, breakpoints) while Safari tabs are completely independent.
I guess I'll close this as WONTFIX since it would mean a bigger change to how we keep app state history. That said, I run into similar disorientation in resources vs debugger tab, so we maybe should revisit this design at some point.</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>