You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having initially reported #46333, I was eager to test the functionality that was implemented in #53915. I came across the following issue that doesn't sound like desirable/intentional behavior.
VSCode Version: 1.26.0
OS Version: Ubuntu 16.04.5 LTS
Steps to Reproduce:
Open the extension sidebar.
Type @ in the search box. An auto-complete menu appears with several possible options (@builtin, @disabled, etc.)
Type or pick one of the options, e.g. @builtin. A list of extensions is shown below.
Select all the text in the box except the @, and delete it
Expected behavior: the initial list of available keywords should appear again.
Actual behavior: The autocomplete list is not shown, and the extension sidebar shows simply "No extensions found."
The text was updated successfully, but these errors were encountered:
Testing on 1.26 just now I'm seeing that simply deleting to the @ does not trigger suggestions, but pressing ctrl+space from there does show the suggestions again. This is as designed, it works the same in the editor: if you type this. suggestions will appear, but if you delete until the period, they wont appear again.
As a side note: you actually don't need to type the @ at all; you can use ctrl+space from the empty search box or any word boundary within the query and it will show suggestions. The @ is simply what we call a trigger character, which means the act of typing it forces suggestions to show, but the act of deleting something up until it does nothing.
Having initially reported #46333, I was eager to test the functionality that was implemented in #53915. I came across the following issue that doesn't sound like desirable/intentional behavior.
Steps to Reproduce:
@builtin
,@disabled
, etc.)@builtin
. A list of extensions is shown below.@
, and delete itExpected behavior: the initial list of available keywords should appear again.
Actual behavior: The autocomplete list is not shown, and the extension sidebar shows simply "No extensions found."
The text was updated successfully, but these errors were encountered: