Re: [w3c/manifest] Should dynamically calculated property values (like `scope` and `start_url`) be programmatically accessible? (#931)

> I think it makes more sense for browser DevTools to display the calculated scope (e.g. Chrome could do so in Application > Manifest) rather than expose the computed value in JS.

Absolutely. Filed https://crbug.com/1108717. 

> Since the developer can explicitly set the scope, ideally they wouldn't have to query it dynamically.

The mentioned use cases from the original post and https://github.com/w3c/manifest/issues/931#issuecomment-662814210 would still be facilitated by providing the data programmatically rather than requiring developers to calculate them. Similar to a service worker's scope, which is exposed [1] despite being calculable. 

——
`(await navigator.serviceWorker.ready).scope`



-- 
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/931#issuecomment-662878515