For years, when I've wanted to search for something in the Visual Studio editor, I have hit Ctrl+F (to bring up the Find dialog) and then immediately, without waiting for the Find dialog to come up, I've started typing what I wanted to search for. It didn't matter if it took a second or two for the Find dialog to come up; without fail, all of the keystrokes I typed after Ctrl+F found their way to the Find: box on the Find dialog.Now, enter Visual Studio 2012, where Find is no longer a dialog box, it's just that little window in the upper-right corner. That's fine, except that now, when I hit Ctrl+F and start typing, the first key I type after Ctrl+F quite often goes into the editor window instead of into the Find box. This is incredibly annoying, on two fronts: First, I'm looking for the wrong thing, and second, I end up with all these stray characters scattered all over my source code. So my I start seeing red squigglies I don't understand, and then when I go to built, I get these compile errors caused by these stray characters.This is a regression.The characteristic whereby all of the characters you type after Ctrl+F were guaranteed to wind up in the Find box needs to be restored in Visual Studio 2012.
Visual Studio/Team Foundation Server/.NET Framework Tooling Version
Steps to reproduce
Operating System Language