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

Something I see as lot of developers trip over is `scope` handling (`start_url` not so much, since it is easier to detect when it does not work as intended). However, developers repeatedly fall for unexpected `scope`s, for example, when they host their manifest from a sub folder.

Would it make sense to expose the [calculated `scope`](https://w3c.github.io/manifest/#ref-for-dfn-application-context-12:~:text=The%20steps%20for%20processing%20the%20scope%20member) via JavaScript (something like `document.manifest.scope`)? This would allow developers to debug and check the `scope`, to, for example, programmatically handle out-of-scope links differently (maybe to add an icon or change the screen orientation,…). 


-- 
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