Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intellisense box (Ctrl+Space) is broken in IE11 #96

Closed
T18970237136 opened this issue Aug 5, 2016 · 5 comments · Fixed by microsoft/vscode#10309
Closed

Intellisense box (Ctrl+Space) is broken in IE11 #96

T18970237136 opened this issue Aug 5, 2016 · 5 comments · Fixed by microsoft/vscode#10309
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@T18970237136
Copy link

Hi,

I noticed a problem with the Monaco Editor in IE11, where the "intellisense box" (sorry, I don't know the correct terminology) doesn't show correctly in IE11.

Steps to reproduce:

  1. Open the Demo Page and select TypeScript as language.
  2. At the top of the file, type Math.
    Result in IE11 and Edge (OK):
    monaco-before


  3. Now press Ctrl + Space.

Actual (IE 11):
monaco-ie11

Expected (Edge):
monaco-edge

Note that after pressing Ctrl+Space, even the other Intellisense window doesn't work again if you move the cursor somewhere and type Math. just like above.

We are using the Monaco Editor in the embedded WebBrowser control in a WPF which unfortunately is bound to IE11 instead of Edge, so it would be nice if Monaco shows correctly in IE11.

Thanks!

@sandyarmstrong
Copy link
Member

sandyarmstrong commented Aug 5, 2016

There are a few ways to trigger this. The key for me seems to make sure that at some point the completion provider returns no results. From that point on, subsequent displays of the completion widget will result in invisible completion items (as displayed above).

Relatedly, on other browsers, if there are no completion results the widget will display "No suggestions." IE11 will not do this.

@sandyarmstrong
Copy link
Member

I wanted to debug this issue but then ran into #97.

@sandyarmstrong
Copy link
Member

Cool, turns out debugging works in Windows 8.1. In the scenario originally reported, the issue is that the tree child of suggest-widgets has display:none.

The message child of suggest-widgets has display:none when the suggest box works and when it malfunctions as described in the original report. But interestingly, it has a text child of "No suggestions" in the latter case. Even though monaco-list-rows is identically populated in both scenarios.

I'll keep digging.

@sandyarmstrong
Copy link
Member

Yay, easy fix. In https://github.com/Microsoft/vscode/blob/master/src/vs/base/browser/dom.ts#L963, in the show function, just change element.style.display = null to element.style.display = ''.

I'll submit a PR.

sandyarmstrong added a commit to sandyarmstrong/vscode that referenced this issue Aug 9, 2016
Setting `element.style.display` to `null` in IE11 has no effect.
So if the suggest widget was hidden for some reason, and then
shown again, it just stayed hidden.

This issue also prevented the "No suggestions" message from displaying.

Fixes: microsoft/monaco-editor#96
sandyarmstrong added a commit to xamarin/vscode that referenced this issue Aug 12, 2016
Setting `element.style.display` to `null` in IE11 has no effect.
So if the suggest widget was hidden for some reason, and then
shown again, it just stayed hidden.

This issue also prevented the "No suggestions" message from displaying.

Fixes: microsoft/monaco-editor#96
@alexdima alexdima added the bug Issue identified by VS Code Team member as probable bug label Aug 16, 2016
@alexdima alexdima added this to the August 2016 milestone Aug 16, 2016
@alexdima alexdima self-assigned this Aug 16, 2016
@T18970237136
Copy link
Author

Thank you!

@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants