Search Everywhere sometimes does not have cursor focus

Pressing SHIFT-SHIFT opens the Search Everywhere dialog however, 1 out of 5 times, the caret focus is not in the input box. This then forces me to use my mouse to click first in the input box then key in my search characters.

In the cases where focus is not there, for an instant I do see the caret in the input box but it immediately disappears.

Ubuntu 16.04

Phpstorm 2017.02.2

 

 

14 comments

This bug is driving me absolutely insane.

Why can't they just use a normal dialog for the search everywhere window? 

6

I am also seeing this issue. It completely disrupts my flow. Please fix!

1

Incredibly annoying bug, please bring out a fix soon!

2

Same here. WebStorm 2017.3, Build #WS-173.3727.108, Ubuntu 17.10

1

Please have a stab at fixing this - one of the best features of the IDE.

1

any news on a fix for this one? its sooo annoying.

0

That's a forum - developers aren't providing any updates here. Please vote/watch https://youtrack.jetbrains.com/issue/IDEA-124160 to receive notifications on the issue status updates.

0

Well, perhaps this is being escalated here since no action has happened on the issue since initial report in 2014(!?), desplte a plenty of votes...
Best, Willy

0

Dmitry, of course I take your word on that, as well as in some of the comments. The status info of the issue, however, does not actually reflect any progress. That's what dormant issues use to look like in our tracker ;-}

Best, Willy

0

+1 for these annoying bug. Please fix it. (unbuntu 16.04 LTS)

0

@Hocq Sylvain

>+1 for these annoying bug. Please fix it. (unbuntu 16.04 LTS)

The aforementioned ticket (https://youtrack.jetbrains.com/issue/IDEA-124160) says it's fixed (in 2018.1 version I believe) ... and quite a few people have confirmed that.

 

What's your IDE version?

If you still have this issue -- please comment there or create new ticket and provide your info (About info + idea.log file (Help | Show Log in XXX)). Maybe it will be related to JDK you are using .. or it could be a completely different cause (and devs/support will show the right ticket/possible workarounds)

1

Please sign in to leave a comment.