| Summary: | Navigator doesn't refresh after creating initial content in HTML5 file system | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Mark Macdonald <mamacdon> |
| Component: | Client | Assignee: | Mark Macdonald <mamacdon> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | libingw, simon_kaegi |
| Version: | 3.0 | Flags: | libingw:
review+
simon_kaegi: review+ |
| Target Milestone: | 3.0 RC3 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Mark Macdonald
The File Explorer didn't understand what to do if explorer.changedItem(item) was called when item equal to the root node, so it didn't refresh. When the root changed, you were expected to call explorer.loadResourceList(item) instead. I made this consistent, so a call to changedItem(root) will refresh the root. This simplified another small piece of code (we no longer need an explicit check to see if loadResourceList() should be called, we can just rely on changedItem() ). Patch here: http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=f3b4492 Tested with patch. The fix is simple and safe. +. An interesting thing I found for the FileExplorer.prototype.changedItem(parent, forceExpand): Only the first time when you add file to an empty folder does it pass the parent as root. If you delete the added file(so you've made the folder empty again) and add the file again, it passes the folder as the parent instead of root. pushed |