[Files.app] Use generateTopLevelEntries() method to retrieve the list on the top level

[Files.app] Use generateTopLevelEntries() method to retrieve the list on the top level

This patch fixes the bug that the directory list is not drawn correctly sometimes.

Previously, DirectoryTree.updateSubDirectories() tries to retrieve an entries from the file system. But the directory structure of the top level is different from the file system, instead, we need to use the special list. This patch change the updateSubDirectories() to use the special list.

BUG=286421
TEST=manual
R=hirono@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=222211

[yoshiki, 2013-09-09 10:42:37]

@hirono: could you take a look? Thanks.

[hirono, 2013-09-10 00:51:13]

https://codereview.chromium.org/23636014/diff/2001/chrome/browser/resources/f...
File chrome/browser/resources/file_manager/js/directory_tree.js (right):

https://codereview.chromium.org/23636014/diff/2001/chrome/browser/resources/f...
chrome/browser/resources/file_manager/js/directory_tree.js:598: recursive,
opt_successCallback, opt_errorCallback) {
opt_errorCallback will not be called.
Can we remove it?

[yoshiki, 2013-09-10 01:01:00]

https://codereview.chromium.org/23636014/diff/2001/chrome/browser/resources/f...
File chrome/browser/resources/file_manager/js/directory_tree.js (right):

https://codereview.chromium.org/23636014/diff/2001/chrome/browser/resources/f...
chrome/browser/resources/file_manager/js/directory_tree.js:598: recursive,
opt_successCallback, opt_errorCallback) {
On 2013/09/10 00:51:13, hirono wrote:
> opt_errorCallback will not be called.
> Can we remove it?

I want to keep the same interface with
DirectoryItem.prototype.updateSubDirectories() since they has the same name.

[hirono, 2013-09-10 01:09:25]

Thanks, lgtm!

[commit-bot: I haz the power, 2013-09-10 01:48:48]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/yoshiki@chromium.org/23636014/2001

[commit-bot: I haz the power, 2013-09-10 02:20:57]

Sorry for I got bad news for ya.
Compile failed with a clobber build on mac.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac&number...
Your code is likely broken or HEAD is junk. Please ensure your
code is not broken then alert the build sheriffs.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2013-09-10 02:30:45]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/yoshiki@chromium.org/23636014/2001

[commit-bot: I haz the power, 2013-09-10 02:39:38]

Sorry for I got bad news for ya.
Compile failed with a clobber build on mac_rel.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_rel&nu...
Your code is likely broken or HEAD is junk. Please ensure your
code is not broken then alert the build sheriffs.
Look at the try server FAQ for more details.

[yoshiki, 2013-09-10 08:32:43]

Committed patchset #2 manually as r222211 (presubmit successful).