The problem here is that the platform's notification design has no way to
understand what the application wants to happen when the user clicks on a
notification.
As a great example - Gmail uses desktop notifications to notify the user
about chat events and new emails. When the user clicks on a
This optional argument sounds reasonable to me (FWIW, I'm working on
the requestAutocomplete implementation for Firefox). The transaction
fields also seem sensible, but I have no experience with payment APIs,
so I can't give feedback on how well this will work with payment
providers in general
Specifically, Chromium would disable Wallet for transactions over a certain
limit (at the moment, that's $2k, but this business logic is subject to
change). When Wallet is disabled, users can still store/access their data
in Chrome/Chrome Sync.
-- Evan Stade
On Wed, Apr 23, 2014 at 5:02 PM,
