I don't know whether it's intended behaviour, but I find it counter-intuitive: When the file browser has the focus, starting a Find (Cmd-F) with search scope 'Document' or 'Selection' does not initiate a search (or give a warning). The expected behaviour is to search in the currently open file (or, if one wants to be fancy, search in the files selected in file browser).
And another anomaly I have just spotted testing this: Having one file open and some text selected and the focus on the editor, opening the Find window with Cmd-F , the Find window opens as expected with 'Selection' as scope. However, actually performing the search finds the needle in a different file within the same project; it'll even open it if it's closed. Strange.
Jonas
On Sep 3, 2012, at 8:02 PM, Jonas Zimmermann listen@jonaszimmermann.de wrote:
When the file browser has the focus, starting a Find (Cmd-F) with search scope 'Document' or 'Selection' does not initiate a search (or give a warning).
This is because it searches “first responder”, e.g. the Find dialog can also search the HTML output window, release notes, or similar, depending on what has focus.
We might be able to do a better job at having the text view be fallback for when the action isn’t applicable to first responder, we do this for key bindings, but that heuristic needs a bit of refining, and if split views are introduced, it’ll be more muddied.