Comments (7)
Update from TPAC: Google would like to move this to FPWD in the next few weeks.
The proposal enables interesting things for payments, but I would appreciate some help with the security and privacy aspects: this does a lot of cross-origin requests and interactions and could have privacy/security implications. So if at all possible, I would like a few of us to discuss what they are proposing before the WG publishes FPWD.
from standards-positions.
Some of my previous thoughts in this space are in the TAG review of Payment Method Manifest, the TAG review of Payment Handler, and a comment in the TAG review of Payment Method Identifiers.
from standards-positions.
I'm inclined to mark this as worth prototyping
. Does that make sense?
from standards-positions.
Makes sense.
from standards-positions.
I'm actually having second thoughts about that. I think given that #23 will be defer
, I think this probably should be as well.
I've also been concerned with this spec in the past about whether it's going to do things in a way that leads to interoperability. That is, does the manifest have enough information for an implementation to understand how to handle the payment method... and is that information specified in the spec.
from standards-positions.
(Or to put it another way -- is it the case that the payment applications linked to either (a) use Payment Handler or (b) don't have a known way to handle payments? Or is there some other mechanism I'm missing here?)
from standards-positions.
"Defer" is good... there is a lot of work to be done on this spec + also the Payment Handler. Once they are in better shape, we can reevaluate our position.
from standards-positions.
Related Issues (20)
- AudioContext.onerror HOT 3
- Allow converting VideoFrame to RGB pixel formats by calling VideoFrame.copyTo() HOT 1
- Still on SerialPort API HOT 3
- The ChapterInformation interface HOT 3
- HTML Fullscreen Without A Gesture
- CSS calc-size() function
- Partitioned Popins HOT 5
- Support Skip-Ad media session action HOT 1
- improved styling of <details> and <summary> elements HOT 2
- CSS Ruby Annotation Layout Module Level 1
- Local Peer-to-Peer API HOT 2
- Timing Info for ServiceWorker static routing API
- New `trusted-types-eval` keyword for CSP script-src HOT 2
- WebGPU: GPUAdapter info attribute HOT 2
- Reference Target for Cross-Root ARIA
- ServiceWorkerAutoPreload
- `noopener-allow-popups` value in COOP
- WebAssembly ESM Integration HOT 1
- Prioritized Task Scheduling: scheduler.yield() HOT 2
- Partitioned :visited links history HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from standards-positions.