@YuAo I saw your pull request, but I misread it and thought it was a bug report. Good catch!

So I fixed this in this commit while I was fixing #6231 . Note that I moved this code a bit in pull request #6258, so your change will have to be merged. I backed out my change for this fix after I noticed that this was actually a pull request :)

The gist of my fix is to also select initial item if any code has been typed (i.e. needle !== ""):

            if (this.primaryTriggerKeys.indexOf(implicitChar) !== -1 ||
                    needle !== "") {
                 selectInitial = true;
            }

But, this fix is not quite right because it prevents Ctrl+space from invoking css property hints when nothing has been typed.

Let me know if you'd like to continue with this, or if I should just fix it.

@redmunds Oh, I didn't notice that. Because my Ctrl+Space is occupied by the input method switch.

I don't think that a code hint is helpful when nothing has been typed. It's better to having no code hint than having a not so useful code hint list floating around.

However, I think we can still fix this by checking the lastContext.

If lastContext is not null, we know that the user has previously typed something and have some hints. So we can get ride of the hint list this time.

If lastContext is null, we know that the user didn't get any hints the last time. We can now show him some hints anyway, if he requires (i.e. pressed Ctrl+Space).

I've added a commit.