- From: Bazin Pascal <Pascal.Bazin@gemalto.com>
- Date: Fri, 3 Mar 2017 08:22:28 +0000
- To: Ian Jacobs <ij@w3.org>
- CC: Payments WG <public-payments-wg@w3.org>
Hi Ian, >> o The user must grant permission to an origin. Should we explain that the permission is possibly bound to a limited payment-app scope. >Is that accurate? (I am asking because I don’t know.) My (incomplete) understanding is that the sort of permissions we are talking about are for the origin. Thus, we don’t have finer >grained permissions. What did you have in mind? Service Worker Register() method allows to specify a 'scope' parameter to limit the access rights range to a subset of the origin. It's not Payment service worker specific therefore probably not worth to mention. >> o Could start with a list of possibly not-supported features. > I don’t understand the comment. Can you provide some examples? In the 'Implementation questions' chapter, you write "We need to learn more about how browsers that don't support features we expect to reference will behave.". It's the bit strange to me (but may be this is the usual way to handle this issue) that if a browser does not support a specification, it will have to support what the spec says about how not to support it ! III Pascal BAZIN ________________________________ This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited. E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender. Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Received on Friday, 3 March 2017 08:23:29 UTC