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

Allow localhost for testing and development. #19

Closed rsolomakhin closed 6 years ago

rsolomakhin commented 6 years ago

For testing and development, allow the (1) payment method identifier, (2) default application URL, and (2) supported origin to be localhost. For example:

Also update the deprecated RFC5988 with its replacement RFC8288, according to bikeshed's error message.

rsolomakhin commented 6 years ago

@domenic please take a look.

domenic commented 6 years ago

I don't think allowing such things at the spec level is the proper way to do things. Probably instead we want to have a developer tools' toggle that goes into a spec-incompliant mode. It'd be quite bad if someone deployed something on the internet that caused browsers to go look up and use payment method manifests on every visitor's machine!

rsolomakhin commented 6 years ago

Can you tell me more about the developer tools toggles? I'm not familiar with these.

domenic commented 6 years ago

Well, so for example, in Chrome's developer tools people have implemented a "Pretend you're offline" switch, or a "Disable cache" switch. We could add similar switches to Chrome if we wanted.

rsolomakhin commented 6 years ago

OK, let's go roll in this direction.