| Summary: | JSLint results missing in IE9 if running from built JS files | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Boris Bokowski <bokowski> |
| Component: | Client | Assignee: | Simon Kaegi <simon_kaegi> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | simon_kaegi |
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Boris Bokowski
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. I fixed the part that generated an error in the console. 0b6f0a11d58fbb7befe05dedae25fd309d4fafec 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. 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. |