How to prevent Find from coming up in a floating window in WebStorm 2017

Starting in the latest WebStorm, when I do a Find operation, it shows up in a floating window (see below).

I want it to be docked by default, like it was before this upgrade. How do I do that?

 

4
10 comments

Hi there,

What do you mean by "docked by default"?

Are you talking about search results? If so --  the preview was available before as well -- but it was separate tab -- now it's part of the actual window. Just click on "Open in Find Window" to see results in separate tool window.

0

By 'docked by default' I mean that, yesterday, my results would not be in a floating window, but with the update, they are now. Clicking on "Open in Find Window" is annoying for me, since I don't want to have to use my mouse every time I do a search. 

One of the main problems I have with this new floating search is that after I've selected and navigated to a result, the search results go away

0

You can switch to the old dialog by deselecting ide.find.as.popup in Registry: Help | Find action, type Registry to locate it, find the option there and deselect the checkbox

4
Avatar
Permanently deleted user

Thank you for the solution to this. 

My issue isn't with the new UI, which is nice; it's having to press Ctrl+Enter now to show the search results in a find tab. Since using Webstorm (with Visual Studio keybindings) for the past 3 years, it's been

Ctrl+Shift+F --> Type Search --> Press Enter --> Results in the results tab.

I've become so accustomed to typing that combination so quickly (both in Webstorm and Visual Studio Code), that I'm always forgetting the Ctrl+Enter at the end now. I'm thus now always having to type my search in a couple of times; once where I just press Enter and something useless happens, and then again with Ctrl+Enter where I get the required functionality.

3
Avatar
Permanently deleted user

All I can say is +1, yes I also want to have an option where my "Find in path ... " always shows up in a Find Window instead of always needing to select the "Open in Find Window" button.  I see that I can type Ctrl-Enter but why do I need to do that every time. 

4
Avatar
Permanently deleted user

I love the floating window - I just don't want it to disappear when I go to one of the search results by double clicking.

Surely a 'stay visible until I close' option would be simple enough.

It's really poor compared to most of the way the IDE is thought out and works.

4
Avatar
Permanently deleted user

Is deselecting `ide.find.as.popup` in Registry still possible with PHP Storm 2020.1.1 ? I cannot see that attribute in the registry.

2

No. This option has been removed in 2019.2. Old style Find in Path dialog is deprecated due to many issues with it, there is no way to re-enable it

0

I'm a very longtime Intellij user and would just like to point out a couple of clear UX issues with this decision. I'd also appreciate correction/advice if I'm getting any of this wrong or if there's an obviously easier way for me to be doing what I want to do.

The popup breaks a consistent UX flow that's present in the rest of the IDE: look for a list of things, and immediately jump to the result locations using next/find occurrence. This flow is currently present with "Search References". It's also present if you explicitly dock the Find results window using "Open in Find Window".

So the current flow may solve for some subtle bugs that affect Jetbrains but is very clearly (to me) broken/inconsistent UX. It just does not make any sense to force users to go through the operation of docking the window in order to use a very basic feature like result navigation. Especially when there's a clear guide to how this all ought to work: the Search References experience.

I would like for request for this to be un-broken.

Or another possible way to address the overall need would be to add result navigation shortcuts to the Find in Path popup dialog (see https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000786390-Find-In-Path-dialog-keyboard-shortcuts).

2

Please sign in to leave a comment.