135587 2014-08-04 17:50:38 -0700 Web Inspector: clicking on some call stack frames doesn't select them 2026-01-12 09:01:25 -0800 1 1 1 Unclassified WebKit Web Inspector 528+ (Nightly build) All All NEW InRadar P2 Normal --- 1 burg webkit-unassigned graouts inspector-bugzilla-changes webkit-bug-importer oldest_to_newest 1026745 0 burg 2014-08-04 17:50:38 -0700 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. 1026746 1 webkit-bug-importer 2014-08-04 17:50:49 -0700 <rdar://problem/17910833> 1026890 2 joepeck 2014-08-05 11:17:04 -0700 Yikes. That sounds really annoying. I'll take a look. 1026910 3 joepeck 2014-08-05 11:56:14 -0700 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. 1026915 4 timothy 2014-08-05 12:08:27 -0700 Yes, a selection in one section should clear the selection in the other section.