Make the sort order in thumbnail view always alphabetical.

Make the sort order in thumbnail view always alphabetical.

Implemented sort related wrapper to ListContainer to fix the actual sort order
in thumbnail view in alphabetical order.

BUG=438915
TEST=sort files non-alphabetically in list view, change view to grid view, and confirm the sort order is alphabetical.
After that, change view to list view, and confirm that the first sort order is restored.

Committed: https://crrev.com/bd854587a2e1b3ca8e7b13299e3d74978b1933f9
Cr-Commit-Position: refs/heads/master@{#307233}

[fukino, 2014-12-05 07:40:29]

fukino@chromium.org changed reviewers:
+ hirono@chromium.org

[fukino, 2014-12-05 07:40:30]

PTAL the CL? Thank you!

[hirono, 2014-12-08 07:29:00]

Can we add browser_tests for the case?
The logic a bit complex.

https://codereview.chromium.org/755363004/diff/1/ui/file_manager/file_manager...
File ui/file_manager/file_manager/foreground/js/ui/list_container.js (right):

https://codereview.chromium.org/755363004/diff/1/ui/file_manager/file_manager...
ui/file_manager/file_manager/foreground/js/ui/list_container.js:109: * @type
{!Object}
Could we use record format ({field: xxx, direction: xxx})?
It looks the object has only two fields.

[fukino, 2014-12-08 10:16:32]

Thanks!
I added a browser_test to check the sort order in grid view.
Could you take another look?

https://codereview.chromium.org/755363004/diff/1/ui/file_manager/file_manager...
File ui/file_manager/file_manager/foreground/js/ui/list_container.js (right):

https://codereview.chromium.org/755363004/diff/1/ui/file_manager/file_manager...
ui/file_manager/file_manager/foreground/js/ui/list_container.js:109: * @type
{!Object}
On 2014/12/08 07:29:00, hirono wrote:
> Could we use record format ({field: xxx, direction: xxx})?
> It looks the object has only two fields.

memo from offline dicsussion: the type for |savedSortStatus_| is inherited from
cr.ui.ArrayDataModel.sortStatus, and the code should handle the case when
savedStatus_.field is undefined or null. I think {!Object} is suitable for the
given situation.

[hirono, 2014-12-08 11:14:42]

lgtm! Thanks!

[fukino, 2014-12-08 11:53:38]

The CQ bit was checked by fukino@chromium.org

[commit-bot: I haz the power, 2014-12-08 11:53:47]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/755363004/20001

[commit-bot: I haz the power, 2014-12-08 12:59:55]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-12-08 13:00:37]

Patchset 2 (id:??) landed as
https://crrev.com/bd854587a2e1b3ca8e7b13299e3d74978b1933f9
Cr-Commit-Position: refs/heads/master@{#307233}

[ilja, 2014-12-10 05:36:18]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/789133002/ by ihf@chromium.org.

The reason for reverting is: Speculative revert for crbug.com/440659..