Post

Yes, that’s the price to pay if you want the web to be a platform that can compete with native apps. Not saying this is bad, but the web would be a much simpler place if we left it just to documents.

But where do you draw the line? Getting the current time in JS also calls out to the OS, which presumably got the time via a “cloud service” (over NTP).

There is a big difference between retrieving something and sending sensitive info. Same reason GPS is safe to use despite it providing a precise location - device is not sending your location to the satellites, it's only retrieving necessary information from them.

All of this is correct except for "Partnered wallets only" on the Payment Request API. Chromium browsers support the Payment Handler API for 3rd-party wallets developer.mozilla.org/en-US/docs/W...

‘Partnered’ here is in the context that you-the-site-owner need to partner with a payment provider.

Beneath that is written "which payment methods work depends entirely on browser vendor partnerships" and my point is you can support any site that designates itself a payment handler. It doesn't even need to use real money. googlechrome.github.io/samples/paym...