-
Notifications
You must be signed in to change notification settings - Fork 745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GOOGLE CHROME] - Clicking a line doesn't navigate to it #3159
Comments
I tried recording in Developer Tools int the Performance section. However, I couldn't get to the scrollIfAnchor function. |
@rbikai, you can try searching in the Call Tree. Note however that it will only find items that are visible in the timeline. Following is an example where I'm zoomed in on a particular area where You could zoom out to the entire timeline to expand the search as shown below where the function is found (bottom of image). |
@idodeclare , thanks for your answer. |
@rbikai, that's good to confirm that something is interfering with OpenGrok's JavaScript. Is there any Chrome extension you're using that might be blocking JS? Or if you're running from a company installation, I wonder if some new Chrome setting would block JS. |
@idodeclare there are no JS settings related that are enforced on the machines. |
Any chance you're using greasemonkey? |
@ktulinger no I'm not, it's not even installed |
@rbikai, perhaps I was premature to accuse JS. I notice now that your URL doesn't seem to include a fragment identifier for the line. E.g., for a URL I tested, after scroll has happened my location shows as ending with The link from the search page would have ended with just e.g. Can you confirm that what you click in the search window has a line-number fragment identifier? (As an aside, not all fragment identifiers survive redirect. The fragment identifier has to have been on a browser link the user clicks. For the recent #3053, to fix where the backend search redirects to a listing with a fragment identifier [e.g. |
I have the same issue. |
I am also seeing the same problem but only with chrome, Mozilla is working fine. |
Exactly the same here |
hi, is there an update to opengrok that fixes this issue on chrome? and I can confirm that if I do what @classigit says then chrome scrolls the page right down to the line number. |
I've never been able to reproduce, and I confirm now it's working fine for me with Chrome version 87.0.4280.88 (Official Build) (x86_64) (macOS). May I ask what version you have? |
Hi @idodeclare - I'm on the same, but Windows. |
Libre Office team generally maintains their public OpenGrok instance at the latest release (within a couple of days). I just succeeded verifying scroll-to-line with the Windows version of Chrome version 87.0.4280.88 (Official Build) (64-bit) via a query of https://opengrok.libreoffice.org/search?full=synchronized&defs=&refs=&path=&hist=&type=&xrd=&nn=19&searchall=true. If you hover over the "served by {OpenGrok" image at the bottom, for releases within the last couple of years or so, OpenGrok pops up the release number and commit hash. E.g. for Libre Office: "1.5.11 - ecb835e". |
Please click that libreoffice query I sent above, and see if scroll-to-line works for you on the resulting links. |
After the latest update of Google Chrome, after searching for anything in opengrok, when you click on a specific line in the search results, it opens the top of the file and doesn't navigate anymore to the line selected.
It works fine in other browsers like Firefox.
Was anyone able to find a workaround or was a solution found for this issue?
The text was updated successfully, but these errors were encountered: