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

Bug 490128

Summary:	[cross file lint] undeclared function errors go away and come back when different file is selected
Product:	[ECD] Orion	Reporter:	Steve Northover <snorthov>
Component:	JS Tools	Assignee:	Curtis Windatt <curtis.windatt.public>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P2
Version:	12.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:
Bug Depends on:	487279
Bug Blocks:

Description Steve Northover

2016-03-21 18:33:20 EDT

I did this on orion.eclipse.org

0) Refresh the browser
0.5) Ensure cross file linting is turned on
1) get org.eclipse.orion.client
2) bundles->org.eclipse.orion.client.cf->web->orion->cfui
3) click on logView.js (NOTE: line 130 addEventListener() is not an error)
4) click on maifestEditor.js (should be right underneath)
5) click back on logView.js
6) BUG: addEventListener() is now an error

Either it is an error all along or it is not.  Either way, clicking around should not change the state.

Comment 1 Curtis Windatt

2016-03-22 10:02:53 EDT

If moving between files causes problems, then this is just another consequence of Bug 487279.  However, I think there is something else going on here because modifying the file at all causes the errors to appear.

Tern can collect more type information as you run requests, so editing the file, moving between files, running ope declaration, etc. all can give Tern more information to make smarter decisions.

Comment 2 Curtis Windatt

2016-03-22 10:16:59 EDT

When the page first loads, Tern thinks that addEventListener is coming from the browser index.  After editing the page, Tern can't find a definition.  Possibly an issue in Tern.

Comment 3 Curtis Windatt

2016-06-29 12:23:45 EDT

The behaviour has been somewhat improved by removing guessed typed from cross file linting.  The error will be shown when the file is first opened and does not change by opening the other file.  However, if you use open impl to get to inputManager the error still disappears.

Comment 4 Michael Rennie

2017-01-10 15:37:27 EST

Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:

https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04002.html