W3C home > Mailing lists > Public > public-payments-wg@w3.org > March 2017

Re: Small updates to proposal [Was: Minutes [Was: [Agenda] 21 Feb 2017 Payment Apps task force call]]

From: Ian Jacobs <ij@w3.org>
Date: Fri, 3 Mar 2017 07:41:56 -0600
Cc: Payments WG <public-payments-wg@w3.org>
Message-Id: <01F9BA2F-32D7-4BE2-B01D-85A394C72162@w3.org>
To: Bazin Pascal <Pascal.Bazin@gemalto.com>

> 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:


Ian Jacobs <ij@w3.org>
Tel: +1 718 260 9447
Received on Friday, 3 March 2017 13:42:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:24 UTC