Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
For "find in files", and even for debugger breakpoints, the correct line number is not brought into focus. The correct line is usually scrolled just off to the top of the visible area (that is, you have to scroll down one line to see the correct line.) This can actually make debugger look hung - because you are at a breakpoint and don't know it.
I'm not able to reproduce this.
Do you have code folding turned on? What if you turn it off?
Code folding is exactly the problem - turning this off gave me correct behavior. Leaving it on caused the line in question (like when you double click the result of a find-in-files) to be scrolled one line above the visible area of the editor.
Works for me in "open" files.
But I can verify that behaviour in file that are not opened & opened by the "find in files" (or other) operations.
Then the editor jumps to the correct line & when the folding updates the line is scrolled off-screen ?
Is that the problem you're seeing ? (Try it out with files that are already open)
You are correct - I don't see the incorrect behavior when the file is already open in the editor - only when it has to be opened.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.