- From: Ian Jacobs <ij@w3.org>
- Date: Fri, 3 Mar 2017 07:41:56 -0600
- To: Bazin Pascal <Pascal.Bazin@gemalto.com>
- Cc: Payments WG <public-payments-wg@w3.org>
> On Mar 3, 2017, at 2:22 AM, Bazin Pascal <Pascal.Bazin@gemalto.com> wrote: > > >>> 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 ! Would this be useful: code showing feature detection and building a fallback page if the feature is not supported? If so, that’s already something we are talking about including in the developer portal under construction: https://github.com/w3c/payment-request-info Ian -- Ian Jacobs <ij@w3.org> https://www.w3.org/People/Jacobs/ Tel: +1 718 260 9447
Received on Friday, 3 March 2017 13:42:04 UTC