<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: ObjectTree Property Path doesn't work for objects logged via console.log"
href="https://bugs.webkit.org/show_bug.cgi?id=143650#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: ObjectTree Property Path doesn't work for objects logged via console.log"
href="https://bugs.webkit.org/show_bug.cgi?id=143650">bug 143650</a>
from <span class="vcard"><a class="email" href="mailto:burg@cs.washington.edu" title="Brian Burg <burg@cs.washington.edu>"> <span class="fn">Brian Burg</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=143650#c3">comment #3</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=143650#c2">comment #2</a>)
> > (In reply to <a href="show_bug.cgi?id=143650#c0">comment #0</a>)
> > > it returns bogus paths, using `this` as the root expression.
> >
> > This is currently expected behavior. "this" is the default when we don't
> > know the value.
> >
> > - Is there a specific case you have in mind that you think we should improve?
> > - Do you think there would be a better default name then "this"?
>
> Well, since the logged object can be previewed, why can't we give it a $n
> binding? It was just confusing to me why some expandable (remote?) objects
> were given numbers and others aren't. If its not possible to bind, maybe
> call it /(value)/ instead of `this`.</span >
And if this would create too many $n bindings, then maybe assign a new one when the object is expanded or right-clicked (or other user interaction to hint a shortcut might be useful).</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>