dpwas: update installability to account for display_override
Takes into account the display_override manifest value when determining if the PWA is installable. For example, if the developer specifies: display: "browser" display_override: ["standalone"] This should be installable, but prior to this change, chromium would only evaluate the display property. Since unsupported values are ignored when parsing the manifest, only the first value in the parsed display_override array needs to be evaluated. To test the change use: chrome --enable-features=WebAppManifestDisplayOverride Example websites: - (not installable) https://mwjacksonmsft.github.io/pwa/display-override-browser/index.html - (installable) https://mwjacksonmsft.github.io/pwa/display-override-custom/index.html Explainer: https://github.com/WICG/display-override/blob/master/explainer.m Design document: https://docs.google.com/document/d/1hEmbGVHMN38q1YTaaGccQ-Y5CHr7xIURYPRWXTuvZLo/edit?usp=sharing I2P: https://groups.google.com/a/chromium.org/d/topic/blink-dev/WvIeZT8uSzw/discussion Bug: 1109520 Change-Id: Ib3f7465ed36474b1166f136c3cd6655cc34add0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2333541 Commit-Queue: Mike Jackson <mjackson@microsoft.com> Reviewed-by:Dominick Ng <dominickn@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#796899}
Showing
Please register or sign in to comment