Re: [w3c/manifest] Relationship between nestedly scoped web app manifests? (#539)

@RobDolinMS  Yep, glad to see the discussion!

I think the feature I mainly requested is pretty similar to 

> In another case, a web app (scope:Chat.Example.com) might have peer subdomains that are in-scope (scope:Music.Example.com and scope:Video.Example.com) but might also have peer domains that are out-of-scope (scope:Events.Example.com)

but focus on paths instead of subdomains. If we take something similar to the proposal of `exclude` from @benfrancis the manifests might look like:

- Taobao PWA's manifest might use:

```
"scope":"h5.m.taobao.com/"
"scope_exclude": ["/trip"],
"start_url":"h5.m.taobao.com/"
“stay_in_app": ["http://login.taobao.com"]
```

- AliTrip PWA's manifest might use:

```
"scope":"h5.m.taobao.com/trip/"
"scope_exclude": ["/sub-app1", "/sub-app2"],
"start_url":"h5.m.taobao.com/trip/home/"
“stay_in_app": ["http://login.taobao.com"]
```

- AliTrip "sub-app" PWA's manifest might use:

```
"scope":"h5.m.taobao.com/trip/sub-app*/"
"start_url":"h5.m.taobao.com/trip/sub-app*/"
“stay_in_app": ["http://login.taobao.com"]
```

In this case, the Alitrip sub-app PWAs could be separated from Alitrip PWA and AliTrip PWA could be separated from Taobao PWA. The browsers could open a new browsing context when navigating to Alitrip from Taobao PWA and vice versa.



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