Bug 135587 - Web Inspector: clicking on some call stack frames doesn't select them
Summary: Web Inspector: clicking on some call stack frames doesn't select them
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2014-08-04 17:50 PDT by Brian Burg
Modified: 2016-12-13 15:32 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Burg 2014-08-04 17:50:38 PDT
If you set a breakpoint in File.js, it creates a tree element for File.js, and places the breakpoint tree element as its child. If you then pause the debugger and one of the call stack entries is at a line within File.js, clicking on that call stack entry will show the resource in the content browser and then select the breakpoint tree element's parent, rather than the call stack entry.

I am guessing that Main.js may not know about the call stack entry's tree element being selected. So, it tries to match fuzzily based on URL.
Comment 1 Radar WebKit Bug Importer 2014-08-04 17:50:49 PDT
<rdar://problem/17910833>
Comment 2 Joseph Pecoraro 2014-08-05 11:17:04 PDT
Yikes. That sounds really annoying. I'll take a look.
Comment 3 Joseph Pecoraro 2014-08-05 11:56:14 PDT
Well, this still selects the call stack entry. The duplicate selection on the resource seems harmless. It is a bit annoying to have what looks like a selection in two places in the sidebar. I think the intent was to have only one selection anywhere in that sidebar.
Comment 4 Timothy Hatcher 2014-08-05 12:08:27 PDT
Yes, a selection in one section should clear the selection in the other section.