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

@marcoscaceres  I love the blog post.  I agree with everything you are saying, however at the same time Manifoldjs is "pollyfilling" the gap between where we are today and where we want to be when progressive apps are a way of life.  two action items:
1. We can remove the notion of script injection.  I was already leery about this, and I feel like it creates a separate layer of code that pulls us away from a progressive app model.  Again, encouraging feature detection, not browser detection.
2. API access.I've gone back and forth between making this something you have to do command line, vs something that you can just include in the manifest behind an mjs_ flag.  I'm working on something that might allow this to go away completely and make a more modern experience (much like you blog post encourages). stay tuned.

@slightlyoff @marcoscaceres  Scope is a tough topic.  I understand now wanting to break the navigation scope, as it has great implications.  However Marcos's example is a valid, we see that with fox news, which use the "extended scope" to include their different news domians, but when chrome picks up the manifest, it isn't the same experience they intend, because of the different domains.  Interesting enough I feel like Gmail is another example. I would want "mail.google.com" to be the app, but I would want "contacts.google.com" to also be part of the app, however I wouldn't want "www.google.com" to be part of the app.  i don't think i can do that with today's spec.  Thoughts?

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