🕸 ️ Add FLAG_ACTIVITY_NEW_DOCUMENT to WebappActivity Intents.
On Samsung Lollipop devices the Intents used to communicate with a foreground WebappActivity were causing a new instance of the WebappActivity to be launched instead of causing onNewIntent of the current Activity to be run. This only occurs when a ChromeTabbedActivity is in the background, when it is not, onNewIntent is called properly. I'm not sure what is special about WebappActivity that causes this - I've been unable to generate a smaller repro. This issue is solved however by making sure both the FLAG_ACTIVITY_NEW_TASK and FLAG_ACTIVITY_NEW_DOCUMENT (which was FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET in pre-Lollipop) have been set on the Intent and FLAG_ONE_SHOT has been set on the PendingIntent. Bug: 846528 Change-Id: I9602537e68b24a186961d29f4c4b1fb1ae9235b0 Reviewed-on: https://chromium-review.googlesource.com/1107631Reviewed-by:Dominick Ng <dominickn@chromium.org> Reviewed-by:
Bernhard Bauer <bauerb@chromium.org> Commit-Queue: Peter Conn <peconn@chromium.org> Cr-Commit-Position: refs/heads/master@{#569286}
Showing
Please register or sign in to comment