Handle MAIN intents in ChromeTabbedActivity.
This is a follow-up to crrev.com/c/667936 which moved MAIN/LAUNCHER
handling into separate .LauncherMain activity alias.
That CL caused existing Chrome app shortcuts to disappear on update.
Turned out that Android launcher creates {MAIN/LAUNCHER, <component>}
intents for app shortcuts (i.e. it bakes in the component), and then
checks that after each update MAIN/LAUNCHER intent for the app resolves
to the shortcut's component. If that check fails, launcher removes the
shortcut.
This means that MAIN/LAUNCHER intents must continue to be handled by
.Main activity alias.
This CL does two renamings:
1. Renames .Main activity alias to .IntentDispatcher alias
2. Renames .LauncherMain alias to .Main
I.e. MAIN/LAUNCHER intents are now handled by .Main alias, making sure
shortcuts won't be removed.
Additionally this CL moves more MAIN categories from .IntentDispatcher
into .Main alias, so that almost all MAIN intents are handled by .Main
(one exception is NOTIFICATION_PREFERENCES, as it needs dispatching).
Bug: 761606
Change-Id: I6cb926c4677758190f743260e11a85129c8863bb
Reviewed-on: https://chromium-review.googlesource.com/700803
Commit-Queue: Dmitry Skiba <dskiba@chromium.org>
Reviewed-by: 
Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506825}
Showing
Please register or sign in to comment