Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 349842 - JSLint results missing in IE9 if running from built JS files
Summary: JSLint results missing in IE9 if running from built JS files
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.2   Edit
Assignee: Simon Kaegi CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-20 11:48 EDT by Boris Bokowski CLA
Modified: 2011-09-01 11:41 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Bokowski CLA 2011-06-20 11:48:35 EDT
I do see the outline information as well as error markers when running an inner, but not when running directly on orion.eclipse.org.

There is a message in the console but not sure which file or line:
LOG: TypeError: Unable to get value of the property 'functions': object is null or undefined
Comment 1 Boris Bokowski CLA 2011-06-20 12:29:29 EDT
There is at least one fix we should do: In outliner.js, we should add a defensive check for resource.data, so that we are not producing an error if it is not available.
Comment 2 Boris Bokowski CLA 2011-06-20 13:42:46 EDT
I fixed the part that generated an error in the console. 0b6f0a11d58fbb7befe05dedae25fd309d4fafec
Comment 3 Simon Kaegi CLA 2011-06-20 16:46:26 EDT
The underlying problem is that the plugin has old metadata associated with it. In this case we need a "pattern" property from the service to know what files the outline applies to.

What's problematic is that our lazy loading of plugins will not reload stale properties. At the moment the user is forced to clear localStorage so we should consider providing a mechanism to reload plugins.
Comment 4 Simon Kaegi CLA 2011-06-20 17:31:01 EDT
We've added a reload capability to the plugin "list" page. This will force the selected plugin (or all plugins if none are selected) to reload their metadata and if necessary update the cache.

We also clear the status message for all successful operations after a 5s delay.