GitLab

Previously the media app had an issue where some operations could
update the launch.js side entryIndex without the receiver.js side
knowing about it, i.e A navigation request is sent to launch.js and
actioned but the media_app has unsaved changes and doesn't load the new
file in. In these cases the user sees file 1 but the entryIndex is
file 2, making navigating to the next file confusing as they jump to
file 3. This CL fixes this by making all navigation requests provide
the file that is currently loaded, launch.js then uses this to inform
what the next file should be rather then relying on the possibly
incorrect entry index.

Google 3 side of this change: cl/327574130
BUG: b/163662946

Change-Id: Iece116c5161b8ba4a2345fe343ce9e343eed986b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366212Reviewed-by: Trent Apted <tapted@chromium.org>
Commit-Queue: Zain Afzal <zafzal@google.com>
Cr-Commit-Position: refs/heads/master@{#800046}