Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 426747

Summary:

[content assist] Incorrect proposals shown after switching editor from .css to .js

Product:

[ECD] Orion

Reporter:

Mark Macdonald <mamacdon>

Component:

Client

Assignee:

Project Inbox <orion.client-inbox>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

normal

Priority:

CC:

antonm, elijahe, Michael_Rennie

Version:

5.0

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
screenshot of irrelevant proposals	none

Description Mark Macdonald

2014-01-27 16:04:05 EST

Created attachment 239361 [details]
screenshot of irrelevant proposals

1. Load a new Orion editor tab on a .css file (or load a .css file then Refresh the page).

2. Now point the editor at a .js file. Best way is to browse to one using Ctrl+Shift+F. You must ensure that the editorView stays alive while you're doing this, if you see the right-hand folder view you'll have to start over.

3. When you've opened the JS file, put the caret after an expression whose type is known and insert a period, for example:
> "foo".

You'll see the entire universe of known JS symbols. I expected only relevant proposals to be shown.

The type inferencer is broken here. Since editor-switching is involved, and it works as expected after reloading the tab, I suspect the host page may be to blame (eg. it's passing incorrect/stale parameters to the provider).

Comment 1 Michael Rennie

2015-01-20 21:08:38 EST

This works for me with the latest in 8.0