From ac397b30791dc90a63a30f2d1d50463ef177b76d Mon Sep 17 00:00:00 2001 From: Thomas Steiner Date: Thu, 5 Aug 2021 13:21:08 +0200 Subject: [PATCH] Make rules clearer https://github.com/WICG/pwa-url-handler/issues/29#issuecomment-892261526 --- src/site/content/en/blog/pwa-url-handler/index.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/site/content/en/blog/pwa-url-handler/index.md b/src/site/content/en/blog/pwa-url-handler/index.md index 3453517d5e9..f0199848672 100644 --- a/src/site/content/en/blog/pwa-url-handler/index.md +++ b/src/site/content/en/blog/pwa-url-handler/index.md @@ -6,7 +6,7 @@ subhead: | authors: - thomassteiner date: 2021-06-03 -updated: 2021-06-29 +updated: 2021-08-05 description: | After registering a PWA as a URL handler, when a user clicks on a hyperlink that matches one of the registered URL patterns, the registered PWA will open. @@ -118,6 +118,9 @@ Since the PWA lives on a different origin (`music.example.com`) than some of the handle (e.g., `https://🎵.example.com`), the app needs to verify ownership of these other origins. This happens in a `web-app-origin-association` file hosted on the other origins. +{% Aside %} Apps that want to handle URLs that live on the _same_ origin than the PWA likewise need to +specify the handling rules in a `web-app-origin-association` file hosted on said origin. {% endAside %} + This file must contain valid JSON. The top-level structure is an object, with a member named `"web_apps"`. This member is an array of objects and each object represents an entry for a unique web app. Each object contains: