Re: [w3ctag/design-reviews] TAG review for web app `scope_extensions` (Issue #875)

Update: I am investigating making 2 modifications to the design.

1. For the case where the same-site format is used in the web app manifest to include a dynamic number of origins, add an additional requirement that response headers from navigation must include the manifest IDs of apps it agrees to be part of. 

2. Allow sites/origins to provide a 'scope' filter in their association files in .well-known path. This allows controlling resources using the same syntax as what is used in manifest scope.

I will update with more details. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/875#issuecomment-2289259544
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/875/2289259544@github.com>