[Payments] Multiple payment apps in single web app manifest.
Before this patch, if a single web app manifest specified multiple sections of "related_applications" with different "id" (package name) fields and the user had several of these payment apps installed, then Chrome would display only one of these payment apps. The problem arose from an erroneous assumption of 1:1 relationship between web app manifests and payment apps. In fact, a single web app manifest can correspond to multiple payment apps, e.g., a dev and a prod version of the same app. The fix is to loop through the full web app manifest when looking for matching payment apps, instead of early-exiting when the first matching payment app is found. After this patch, if a single web app manifest specified multiple sections of "related_applications" with different "id" fields and the user had several of these payment apps installed, then Chrome displays all of the matching payment apps. Bug: 745765 Change-Id: I70f287cb792ac8b0b073c22e9c08eebec6ffae3e Reviewed-on: https://chromium-review.googlesource.com/579964Reviewed-by:Ganggui Tang <gogerald@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#488399}
Showing
Please register or sign in to comment