[PWAs as URL handler article] Make same origin rules clearer (#5929)

* Make rules clearer WICG/pwa-url-handler#29 (comment) * Update src/site/content/en/blog/pwa-url-handler/index.md Co-authored-by: Joe Medley <[email protected]> Co-authored-by: Joe Medley <[email protected]>
GoogleChrome · Aug 6, 2021 · 3c238e2 · 3c238e2
1 parent 44c30ac
commit 3c238e2
Showing 1 changed file with 4 additions and 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
@@ -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 as 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: