Re: [manifest] Handleing capabilities with Manifoldjs (#412)

Personally, I am a bit afraid of the custom script stuff, especially if others repackage it, and I think there needs to be a requirements like the manifest MUST live on the same server as the start_url.

Now, as devs don't submit a URL to the stores but use Manifoldjs, it also means that people can modify the tool quite easily - so I don't know how to get around that easily.

I would also leave out "platform" from custom scripts. People can already do checks in the JavaScript file themselves via the userAgent string and that is much more flexible. I don't think that we want to add anything else like that to the platform.

It is unclear when the script will be loaded, maybe the key name could make that more clear.

https://developer.mozilla.org/en-US/docs/Web/API/WorkerGlobalScope/importScripts

Maybe we should name it "mjs_import_scripts".

"mjs_import_scripts": [
  { "src": "js/barcode-scanner.js" },
  { "src": "http://mydomain.com/js/photo-capture.js", "target": ["/pictures/*", "/user/profile"] } 
]

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/412#issuecomment-155706759