Skip to content

Commit 71e2cea

Browse files
committed
link text match destination title
1 parent 6e38ddb commit 71e2cea

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ The manifest of a PWA defines which part of the hosting domain the PWA is scoped
4848

4949
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`.
5050

51-
**Note**: The scope extensions feature is currently in [Origin Trials](./origin-trials.md). To find out more about the state of development of this feature in Chromium, check out the [Web app scope extensions feature](https://chromestatus.com/feature/5746537956114432) at Chrome Platform Status.
51+
**Note**: The scope extensions feature is currently in origin trial. See [Experimental features and origin trials](./origin-trials.md). To find out more about the state of development of this feature in Chromium, check out the [Web app scope extensions feature](https://chromestatus.com/feature/5746537956114432) at Chrome Platform Status.
5252

5353
Once the feature can be used in Microsoft Edge, we will document it here. In the meantime, to learn more about how scope extensions will work, see [the explainer document on the WICG repository](https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md).
5454

0 commit comments

Comments
 (0)