Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95)

> On 25 Jan 2017, at 12:45 am, ianbjacobs <notifications@github.com> wrote:
> 
> @marcoscaceres wrote:
> 
> "Isn't that just duplicating HTML (link rel=icon and meta application-name) and web manifest? "
> 
> That's the issue that triggered all this. :) We would like to use Web Manifest.
> 

You don't need to do anything then. It's part of the web platform - just assume it's there. Like you assume HTML, CSS, JS, Service Workers, URL, DOM, Fetch, Caches, Encoding, Unicode, etc. are there.

We don't need special provisions for the above - we don't need anything about manifest either. 

> Web Manifest is partly implemented and there are statements of intention to implement. We have been wondering how to manage a transition period where we want people to be able to create payment apps (and use icons, etc.) 
> 

Again, you don't need to "manage" that. All the browser vendors know about it and each browser vendor provides a fallback. 

It's a solved problem; and where it is not, implementers can bring feature requests to the Web Manifest spec. But again, it's outside the scope of this WG - and more reason to drop the "app" postfix for this feature. 
> even before Web Manifest is widely deployed. I'd like to figure out how to do that as cleanly as possible.
> 
Cleanest solution is to do nothing. Focus just on solving responding to payment requests. 

> Ian
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
> 


-- 
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/webpayments-payment-apps-api/issues/95#issuecomment-274814624