From b3be8b6d7406f6263c44a635598a3a2027976226 Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 09:10:36 -0700 Subject: [PATCH 01/14] draft --- .../how-to/handle-urls.md | 47 +++++++++++++++---- 1 file changed, 38 insertions(+), 9 deletions(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index bda1893243..a497f3b43e 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -6,7 +6,7 @@ ms.author: msedgedevrel ms.topic: conceptual ms.service: microsoft-edge ms.subservice: pwa -ms.date: 09/15/2022 +ms.date: 08/12/2025 --- # Handle links to a PWA @@ -44,20 +44,49 @@ No code is required for automatic link handling to work, but end users can opt-o ## Handle links from other origins by using scope extensions -Scope extensions make it possible for a PWA to capture navigation to paths, subdomains, or even sites other than its own scope. This can be useful for PWAs that span multiple domains for localization purposes. For example, a PWA may span `contoso.com`, `contoso.co.uk`, and `contoso.fr`. +Scope extensions make it possible for a Progressive Web App (PWA) to capture navigation to paths, subdomains, or even sites other than its own scope. Scope extensions allow web apps that rely on multiple subdomains and top-level domains to be presented as a single web app. This can be useful for PWAs that span multiple domains for localization purposes. -The manifest of a PWA defines which part of the hosting domain the PWA is scoped to. For example, the `www.contoso.com` domain name may have a PWA defined under `www.contoso.com/app` with its scope set to `/app`. In this case, all the web pages available within the `www.contoso.com/app` path are part of the PWA scope. However, the web pages within the `www.contoso.com/foo` path are not part of the PWA scope. Furthermore, web pages that are available at `bar.contoso.com/app` or `www.contoso.co.uk` are also not part of the PWA scope. +For example, a PWA may span all of the following top-level domains: +* `contoso.com` +* `contoso.co.uk` +* `contoso.fr` +The manifest of a PWA defines which part of the hosting domain the PWA is scoped to. For example, the `www.contoso.com` domain name may have a PWA defined under `www.contoso.com/app`, with its scope set to `/app`. - -#### Origin trial +In that case, all webpages within the `www.contoso.com/app` path are part of the PWA scope. However: -As of October 17, 2024, the scope extensions feature is an origin trial. For status, see [Web app scope extensions feature](https://chromestatus.com/feature/5746537956114432) at Chrome Platform Status. +* Webpages within the `www.contoso.com/foo` path are not part of the PWA scope. +* Webpages that are available at `bar.contoso.com/app` or `www.contoso.co.uk` are not part of the PWA scope. -When the feature can be used in Microsoft Edge and is no longer in origin trial, the feature will be documented in the present article. See [Scope Extensions for Web Apps](https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md), an Explainer in the **manifest-incubations** repo. -See also: -* [Use origin trials in Microsoft Edge](../../origin-trials/index.md) + +#### The `scope_extensions` web app manifest member + +The `scope_extensions` web app manifest member enables a web app to extend its scope to other origins. + +```json +{ + "name": "Example app", + "display": "standalone", + "start_url": "/index.html", + "scope_extensions": [ + { + "type": "type", + "origin": "https://example.com" + } + ] +} +``` + +The origins that are listed in the `scope_extensions` member must confirm that they are associated with the web app by hosting a configuration file named `.well-known/web-app-origin-association`. The file must list the web app's origin: + +```json +{ + "https://sample-app.com/": { + "scope": "/" + } +} +``` From b46abcfd1f647b2dfd4ef98110aaa5c958ce83e9 Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 09:36:56 -0700 Subject: [PATCH 02/14] eg location of config files --- microsoft-edge/progressive-web-apps/how-to/handle-urls.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index a497f3b43e..491be46b4a 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -62,7 +62,7 @@ In that case, all webpages within the `www.contoso.com/app` path are part of the #### The `scope_extensions` web app manifest member -The `scope_extensions` web app manifest member enables a web app to extend its scope to other origins. +The `scope_extensions` web app manifest member enables a web app to extend its scope to other origins. For example, this web app manifest file resides at `sample-app.com`, and extends the scope to a different origin, `example.com`: ```json { @@ -78,7 +78,9 @@ The `scope_extensions` web app manifest member enables a web app to extend its s } ``` -The origins that are listed in the `scope_extensions` member must confirm that they are associated with the web app by hosting a configuration file named `.well-known/web-app-origin-association`. The file must list the web app's origin: +The origins that are listed in the `scope_extensions` member must confirm that they are associated with the web app by hosting a configuration file named `.well-known/web-app-origin-association`. The configuration file must list the web app's origin. + +For example, this `.well-known/web-app-origin-association` configuration file resides at `example.com`, and lists the web app's origin as `sample-app.com`: ```json { From c53f666db13a6038ac62d942b75c7197021bc0eb Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 10:14:16 -0700 Subject: [PATCH 03/14] expand scenario details --- .../how-to/handle-urls.md | 40 ++++++++++++++++--- 1 file changed, 34 insertions(+), 6 deletions(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index 491be46b4a..572d8b9575 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -44,19 +44,47 @@ No code is required for automatic link handling to work, but end users can opt-o ## Handle links from other origins by using scope extensions -Scope extensions make it possible for a Progressive Web App (PWA) to capture navigation to paths, subdomains, or even sites other than its own scope. Scope extensions allow web apps that rely on multiple subdomains and top-level domains to be presented as a single web app. This can be useful for PWAs that span multiple domains for localization purposes. +Scope extensions make it possible for a Progressive Web App (PWA) to capture navigation to domains, subdomains, or paths other than its own scope. Scope extensions allow web apps that rely on multiple top-level domains, multiple subdomains, or multiple paths to be presented as a single web app. -For example, a PWA may span all of the following top-level domains: +Scope extension can be useful for localization purposes, for a PWA that spans multiple domains, subdomains, or paths. + + + +#### PWA scope when not using scope extensions + +The manifest of a PWA defines which part of the hosting domain, such as a specific path, the PWA is scoped to. For example, the `www.contoso.com` domain name may have a PWA defined under the path `www.contoso.com/app`, with its scope set to `/app`. + +In that case, all webpages within the `www.contoso.com/app` path are part of the PWA scope. However, if you don't use scope extensions: + +* Webpages at a different domain, such as `www.contoso.co.uk`, are not part of that PWA scope. +* Webpages at a different subdomain, such as `bar.contoso.com/app`, are not part of that PWA scope. +* Webpages at a different path, such as `www.contoso.com/foo`, are not part of the PWA scope. + + + +#### Extending scope to other domains + +By using scope extensions, a PWA may span all of the following top-level domains: * `contoso.com` * `contoso.co.uk` * `contoso.fr` -The manifest of a PWA defines which part of the hosting domain the PWA is scoped to. For example, the `www.contoso.com` domain name may have a PWA defined under `www.contoso.com/app`, with its scope set to `/app`. -In that case, all webpages within the `www.contoso.com/app` path are part of the PWA scope. However: + +#### Extending scope to other subdomains + +By using scope extensions, a PWA may span all of the following subdomains: +* `www.contoso.com` +* `bar.contoso.com` +* `www.contoso.co.uk` + + + +#### Extending scope to other paths -* Webpages within the `www.contoso.com/foo` path are not part of the PWA scope. -* Webpages that are available at `bar.contoso.com/app` or `www.contoso.co.uk` are not part of the PWA scope. +By using scope extensions, a PWA may span all of the following paths: +* `www.contoso.com/app` +* `www.contoso.com/foo` From 0d807ab82d9b2001675ffb77038eed6aa08dacef Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 10:23:59 -0700 Subject: [PATCH 04/14] remove path from subdomain example --- microsoft-edge/progressive-web-apps/how-to/handle-urls.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index 572d8b9575..a5b88a8c24 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -57,7 +57,7 @@ The manifest of a PWA defines which part of the hosting domain, such as a specif In that case, all webpages within the `www.contoso.com/app` path are part of the PWA scope. However, if you don't use scope extensions: * Webpages at a different domain, such as `www.contoso.co.uk`, are not part of that PWA scope. -* Webpages at a different subdomain, such as `bar.contoso.com/app`, are not part of that PWA scope. +* Webpages at a different subdomain, such as `bar.contoso.com`, are not part of that PWA scope. * Webpages at a different path, such as `www.contoso.com/foo`, are not part of the PWA scope. From dde8737879b3be4f35f20d871fb5a6ad415ce583 Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 10:25:13 -0700 Subject: [PATCH 05/14] remove domain from list of subdomains --- microsoft-edge/progressive-web-apps/how-to/handle-urls.md | 1 - 1 file changed, 1 deletion(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index a5b88a8c24..2c5ecff06c 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -76,7 +76,6 @@ By using scope extensions, a PWA may span all of the following top-level domains By using scope extensions, a PWA may span all of the following subdomains: * `www.contoso.com` * `bar.contoso.com` -* `www.contoso.co.uk` From 1bf1ddcb0e9d5bf27c6958f156da79c32a2dfba3 Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 10:34:40 -0700 Subject: [PATCH 06/14] restore explainer link --- microsoft-edge/progressive-web-apps/how-to/handle-urls.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index 2c5ecff06c..a4647415d4 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -117,6 +117,9 @@ For example, this `.well-known/web-app-origin-association` configuration file re } ``` +See also: +* [Scope Extensions for Web App Manifest](https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md) - explainer. + ## See also From bab39978cbf835ef8b1cb4d4894aaddad9bcdaf9 Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 10:44:11 -0700 Subject: [PATCH 07/14] refactor dup text in list --- microsoft-edge/progressive-web-apps/how-to/handle-urls.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index a4647415d4..b605adf880 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -54,11 +54,11 @@ Scope extension can be useful for localization purposes, for a PWA that spans mu The manifest of a PWA defines which part of the hosting domain, such as a specific path, the PWA is scoped to. For example, the `www.contoso.com` domain name may have a PWA defined under the path `www.contoso.com/app`, with its scope set to `/app`. -In that case, all webpages within the `www.contoso.com/app` path are part of the PWA scope. However, if you don't use scope extensions: +In that case, all webpages within the `www.contoso.com/app` path are part of the PWA scope. However, if you don't use scope extensions, the following webpages are not part of that PWA scope: -* Webpages at a different domain, such as `www.contoso.co.uk`, are not part of that PWA scope. -* Webpages at a different subdomain, such as `bar.contoso.com`, are not part of that PWA scope. -* Webpages at a different path, such as `www.contoso.com/foo`, are not part of the PWA scope. +* Webpages at a different domain, such as `www.contoso.co.uk`. +* Webpages at a different subdomain, such as `bar.contoso.com`. +* Webpages at a different path, such as `www.contoso.com/foo`. From ce980e14542766bfc9ef60373dfd9542c7ad9f7a Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 10:45:21 -0700 Subject: [PATCH 08/14] avoid 'may' --- microsoft-edge/progressive-web-apps/how-to/handle-urls.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index b605adf880..9dc3cb44bf 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -64,7 +64,7 @@ In that case, all webpages within the `www.contoso.com/app` path are part of the #### Extending scope to other domains -By using scope extensions, a PWA may span all of the following top-level domains: +By using scope extensions, a PWA can span all of the following top-level domains: * `contoso.com` * `contoso.co.uk` * `contoso.fr` @@ -73,7 +73,7 @@ By using scope extensions, a PWA may span all of the following top-level domains #### Extending scope to other subdomains -By using scope extensions, a PWA may span all of the following subdomains: +By using scope extensions, a PWA can span all of the following subdomains: * `www.contoso.com` * `bar.contoso.com` @@ -81,7 +81,7 @@ By using scope extensions, a PWA may span all of the following subdomains: #### Extending scope to other paths -By using scope extensions, a PWA may span all of the following paths: +By using scope extensions, a PWA can span all of the following paths: * `www.contoso.com/app` * `www.contoso.com/foo` From 010014625a5867431a695cddb201a4c681687165 Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 10:48:24 -0700 Subject: [PATCH 09/14] example is domains --- microsoft-edge/progressive-web-apps/how-to/handle-urls.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index 9dc3cb44bf..fd8b161e23 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -89,7 +89,7 @@ By using scope extensions, a PWA can span all of the following paths: #### The `scope_extensions` web app manifest member -The `scope_extensions` web app manifest member enables a web app to extend its scope to other origins. For example, this web app manifest file resides at `sample-app.com`, and extends the scope to a different origin, `example.com`: +The `scope_extensions` web app manifest member enables a web app to extend its scope to other origins. For example, this web app manifest file resides at the domain `sample-app.com`, and extends the scope to a different domain, `example.com`: ```json { @@ -107,7 +107,7 @@ The `scope_extensions` web app manifest member enables a web app to extend its s The origins that are listed in the `scope_extensions` member must confirm that they are associated with the web app by hosting a configuration file named `.well-known/web-app-origin-association`. The configuration file must list the web app's origin. -For example, this `.well-known/web-app-origin-association` configuration file resides at `example.com`, and lists the web app's origin as `sample-app.com`: +For example, this `.well-known/web-app-origin-association` configuration file resides at the domain `example.com`, and lists the web app's origin as the domain `sample-app.com`: ```json { From 3daca19436f3c7c84e8380f7b2b88cb31a2baef0 Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 10:49:38 -0700 Subject: [PATCH 10/14] strike 'all of' --- microsoft-edge/progressive-web-apps/how-to/handle-urls.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index fd8b161e23..dac20ba83c 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -64,7 +64,7 @@ In that case, all webpages within the `www.contoso.com/app` path are part of the #### Extending scope to other domains -By using scope extensions, a PWA can span all of the following top-level domains: +By using scope extensions, a PWA can span the following top-level domains: * `contoso.com` * `contoso.co.uk` * `contoso.fr` @@ -73,7 +73,7 @@ By using scope extensions, a PWA can span all of the following top-level domains #### Extending scope to other subdomains -By using scope extensions, a PWA can span all of the following subdomains: +By using scope extensions, a PWA can span the following subdomains: * `www.contoso.com` * `bar.contoso.com` @@ -81,7 +81,7 @@ By using scope extensions, a PWA can span all of the following subdomains: #### Extending scope to other paths -By using scope extensions, a PWA can span all of the following paths: +By using scope extensions, a PWA can span the following paths: * `www.contoso.com/app` * `www.contoso.com/foo` From 99bca929bd4132a023d60d2275e7237bcc79c088 Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 10:52:09 -0700 Subject: [PATCH 11/14] strike 'explainer', no net gain clarity --- microsoft-edge/progressive-web-apps/how-to/handle-urls.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index dac20ba83c..93dced81ae 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -118,7 +118,7 @@ For example, this `.well-known/web-app-origin-association` configuration file re ``` See also: -* [Scope Extensions for Web App Manifest](https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md) - explainer. +* [Scope Extensions for Web App Manifest](https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md) From 3ce21760f32f59aa757af46b764b987454eb10ea Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 10:57:49 -0700 Subject: [PATCH 12/14] new para at For example --- microsoft-edge/progressive-web-apps/how-to/handle-urls.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index 93dced81ae..c629891326 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -89,7 +89,9 @@ By using scope extensions, a PWA can span the following paths: #### The `scope_extensions` web app manifest member -The `scope_extensions` web app manifest member enables a web app to extend its scope to other origins. For example, this web app manifest file resides at the domain `sample-app.com`, and extends the scope to a different domain, `example.com`: +The `scope_extensions` web app manifest member enables a web app to extend its scope to other origins. + +For example, this web app manifest file resides at the domain `sample-app.com`, and extends the scope to a different domain, `example.com`: ```json { From 7233676c97888cb066eca02ac77c5208aeaca6e8 Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Tue, 12 Aug 2025 12:47:03 -0700 Subject: [PATCH 13/14] condense 3 example sections --- .../progressive-web-apps/how-to/handle-urls.md | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index c629891326..3934d1119e 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -62,26 +62,20 @@ In that case, all webpages within the `www.contoso.com/app` path are part of the -#### Extending scope to other domains +#### Extending scope to other domains, subdomains, or paths -By using scope extensions, a PWA can span the following top-level domains: +By using scope extensions, a PWA can span other domains, subdomains, or paths. For example: + +A PWA can span the following top-level domains: * `contoso.com` * `contoso.co.uk` * `contoso.fr` - - -#### Extending scope to other subdomains - -By using scope extensions, a PWA can span the following subdomains: +A PWA can span the following subdomains: * `www.contoso.com` * `bar.contoso.com` - - -#### Extending scope to other paths - -By using scope extensions, a PWA can span the following paths: +A PWA can span the following paths: * `www.contoso.com/app` * `www.contoso.com/foo` From 3cce97fa81a7895894bd7ef08bc62b6791861dbf Mon Sep 17 00:00:00 2001 From: "Michael S. Hoffman" Date: Fri, 29 Aug 2025 12:02:47 -0700 Subject: [PATCH 14/14] inc rvw --- .../progressive-web-apps/how-to/handle-urls.md | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md index 3934d1119e..7fffd50e17 100644 --- a/microsoft-edge/progressive-web-apps/how-to/handle-urls.md +++ b/microsoft-edge/progressive-web-apps/how-to/handle-urls.md @@ -6,7 +6,7 @@ ms.author: msedgedevrel ms.topic: conceptual ms.service: microsoft-edge ms.subservice: pwa -ms.date: 08/12/2025 +ms.date: 08/29/2025 --- # Handle links to a PWA @@ -46,7 +46,7 @@ No code is required for automatic link handling to work, but end users can opt-o Scope extensions make it possible for a Progressive Web App (PWA) to capture navigation to domains, subdomains, or paths other than its own scope. Scope extensions allow web apps that rely on multiple top-level domains, multiple subdomains, or multiple paths to be presented as a single web app. -Scope extension can be useful for localization purposes, for a PWA that spans multiple domains, subdomains, or paths. +Scope extension can be useful for cases such as PWAs that handle localization by using multiple domains, subdomains, or paths. @@ -94,7 +94,7 @@ For example, this web app manifest file resides at the domain `sample-app.com`, "start_url": "/index.html", "scope_extensions": [ { - "type": "type", + "type": "origin", "origin": "https://example.com" } ] @@ -114,10 +114,5 @@ For example, this `.well-known/web-app-origin-association` configuration file re ``` See also: +* [scope_extensions](https://developer.mozilla.org/docs/Web/Progressive_web_apps/Manifest/Reference/scope_extensions) at MDN. * [Scope Extensions for Web App Manifest](https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md) - - - -## See also - -* [PWAs as URL Handlers](https://web.dev/pwa-url-handler/)