w3c payment-method-manifest issues

w3c / payment-method-manifest

Specification for Web Payments payment method manifests

https://w3c.github.io/payment-method-manifest/

Other

9 stars 13 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Renaming master branch

#46 ianbjacobs closed 3 years ago
2
Remove "*" functionality for supported_origins

#45 danyao closed 4 years ago
3
Spec cleanup for "default_applications"

#44 rsolomakhin closed 2 years ago
3
Allow additional properties in manifest

#43 adrianhopebailie opened 4 years ago
4
Remove "*" functionality for supported_origins

#42 danyao closed 4 years ago
1
"serviceworker" member no longer a thing

#41 marcoscaceres opened 4 years ago
0
Manifest's (c|s)hould be optional for payment handlers

#40 cyberphone opened 4 years ago
0
Meta: attempt alternate deploy key strategy

#39 domenic closed 5 years ago
0
URL resolution may be wrong

#38 domenic closed 5 years ago
1
Allow the PMI URL to directly contain the PMM

#37 domenic closed 5 years ago
3
Editorial: use new Infra primitives for parsing JSON

#36 domenic closed 5 years ago
0
Build using Travis CI, and other boilerplate updates

#35 domenic closed 5 years ago
0
Restrict origin of "default_applications"

#34 rsolomakhin opened 5 years ago
3
For HEAD request on identifierURL, redact URL for privacy

#33 ianbjacobs opened 5 years ago
1
Remove extra comma from w3c.json file

#32 sideshowbarker closed 5 years ago
1
Added for repo management

#31 ianbjacobs closed 5 years ago
1
Redesign of "extract header list values" expected

#30 annevk opened 6 years ago
0
Regular expressions for "supported_origins"

#29 rsolomakhin opened 6 years ago
0
Allow following redirects when requesting payment method ‘HEAD’

#28 gogerald opened 6 years ago
7
Should this be a part of web app manifest?

#27 rsolomakhin opened 6 years ago
4
Terms and conditions text to be displayed near Pay button

#26 ianbjacobs opened 6 years ago
0
Relative URL for "default_applications"

#25 rsolomakhin closed 6 years ago
3
Hosting on localhost

#24 rsolomakhin closed 6 years ago
0
Clarify referrer policy

#23 marcoscaceres closed 6 years ago
5
Fetches should probably use CORS

#22 domenic closed 7 years ago
3
Perform fetches with a supplied client

#21 domenic closed 7 years ago
2
Suggest how to deal with issue 7.

#20 rsolomakhin closed 7 years ago
8
Allow localhost for testing and development.

#19 rsolomakhin closed 7 years ago
5
Use "parse JSON from bytes"

#18 annevk closed 7 years ago
0
Suggest rephrasing language for web developers

#17 ianbjacobs closed 7 years ago
2
Updating references to other payments specs

#16 ianbjacobs closed 7 years ago
2
Front matter needs adjusting for W3C FPWD

#15 ianbjacobs closed 6 years ago
7
Ian edits to prepare for FPWD

#14 ianbjacobs closed 7 years ago
3
Reference URL in section on IANA considerations

#13 ianbjacobs opened 7 years ago
3
Converted from bikeshed to respec

#12 ianbjacobs closed 7 years ago
5
Matching payment apps and security in a world of payment method manifests

#11 ianbjacobs opened 7 years ago
9
reconsider extra level of indirection for retrieving a manifest?

#10 dbaron closed 5 years ago
8
"Unicode serialization" definition has been removed

#9 dbaron closed 7 years ago
0
Update Repository that the document lives in.

#8 dbaron closed 7 years ago
2
Privacy considerations of retrieving a payment method manifest

#7 triblondon closed 7 years ago
2
Minor editorial suggestions

#6 ianbjacobs closed 7 years ago
2
Migrate to a W3C org?

#5 RByers closed 7 years ago
6
Don't forget to do the IANA link relation registration dance

#4 domenic closed 7 years ago
0
Use the first Link header if multiple match our requirements

#3 domenic closed 7 years ago
0
Link URLs should be parsed relative

#2 domenic closed 7 years ago
0
Should these fetches have a client? (impacts CSP, CORS, ...)

#1 domenic closed 7 years ago
18