Option to 'Hide Find and Replace window...' is missing from Visual Studio 2012 - by bukbukbukark

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 779182 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/13/2013 5:51:37 PM
Access Restriction Public


Visual Studio 2012 is missing the option to 'Hide Find and Replace window after a match is located for Quick Find or Quick Replace'. This option was in Visual Studio 2008, under Environment / Find and Replace, and when turned on it immediately removes the Quick Find or Quick Replace window and returns focus to the editor (this was the default behavior in earlier versions of VS if I remember correctly).

In VS 2012 it seems you have no option but to manually return focus to the editor, which is clumsy and difficult to adjust to after using previous versions of Visual Studio for so long.
Sign in to post a comment.
Posted by Microsoft on 6/22/2015 at 6:09 PM
Thanks to all who have voted and commented so far on this bug.

We rank issues which have existed for some time according to their customer impact as measured by number of votes and other mentions for the issue in feedback.

We're continuing to watch this issue to see if it recieves sufficient feedback to rank above other candidates for a fix.


Mark Wilson-Thomas
Program Manager, Visual Studio Editor
Posted by George Menhorn on 4/28/2015 at 4:21 PM
This still appears to be a problem in Visual Studio 2013 Update 4. Will this be fixed at some point?
Posted by Microsoft on 2/25/2013 at 7:28 AM

Thank you for logging this issue. We will definitely consider fixing this issue for future versions. I am marking this bug as copied to our backlog. Please feel free to vote up this issue.

Murali Krishna Hosabettu Kamalesha | Program Manager | Visual Studio Professional - Editor team
Posted by Microsoft on 2/13/2013 at 11:55 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/13/2013 at 6:52 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)