Re: [w3c/manifest] Scope: Allow developer to have more fine-grained control of app scope. (#996)

I see there's renewed interest in refining how navigation scope is defined.

It's a decade old now, but a long time ago I did a [study](https://docs.google.com/document/d/1fOsQWOOVuKyqO7cXZoKmxZGQ9FLgLMwmCRw3OEqIKrQ/edit?usp=sharing) of URL scope in web applications from what were then the top web sites/web apps on the Chrome Web Store, Firefox Marketplace and Alexa Top 20.

Whilst that study is now very out of date, the [proposed solutions](https://github.com/w3c/manifest/issues/114#issuecomment-63064364) derived from that report may still be useful.

Some factors to think about:
- Which URLs are _included_ as part of the app
- Which URLs are _excluded_ as part of the app
- Which URLs should result in navigations from outside the app being _captured_ by the app
- Which URLs should result in navigations from inside the app to _stay in_ the app
- What is used as the default scope when one is not provided

An example solution:

```json
{
  "start_url”: “https://foo.com/",
  "scope": {
    "include": ["/foo", "/bar"],
    "exclude": ["/foo/baz", "/bar/qux"]
  },
  "stay_in_app": ["https://norf.com"]
}
```

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/996#issuecomment-2427175974
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/996/2427175974@github.com>