[Webkit-unassigned] [Bug 104927] New: Web Inspector: "Search sources" click link fails

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=104927

           Summary: Web Inspector: "Search sources" click link fails
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: johnjbarton at chromium.org
                CC: keishi at webkit.org, pmuellr at yahoo.com,
                    pfeldman at chromium.org, yurys at chromium.org,
                    apavlov at chromium.org, loislo at chromium.org,
                    vsevik at chromium.org,
                    web-inspector-bugs at googlegroups.com


This is a long standing bug in navigating the multi-file search results.  Very frustrating and common.

1. Open devtools on devtools in a Chromium (from source) build.
2. Shift Control F and type "scope" into the "Search sources" input box.
3. Scroll to the bottom of the results, you should see a disclosure triangle and ScriptsSearchScope.js.
4. Open the triangle for ScriptsSearchScope.js. You should see one result, the rest are hidden below (ok that's another bug, we should see as many results as will fit in the window).
5. Click on the first result. Navigation succeeds.
6. Click on the last result. 

Expected: navigation to the corresponding line.
Actual: The search results panel does something funky. Scroll to top?

Second click on last line succeeds.

First line of results for ScriptsSearchScope.js click again, suceeds, but the last result again fails.

I've not looked at the code, but my guess is that the failing case does partial work, but fails to bring the result in to view. Thus the next click after a failure succeeds even though a click on the same result line might fail at another time. This context-dependence is why this bug is hard to reproduce and why quick testing may lead a developer to think the bug is fixed.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.