Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351)

> thanks @danyao !
> 
> Some other thoughts / questions:
> 
> 1. Is there a payer can opt to not prompt the user for 1p storage?  I'm comfortable with the 'prompt-but-default-off' compromise reached above, but there should be a way for handlers to not prompt (e.g. only be used in 3p contexts), parallel to what would happen in an iframe that never called `document.requestStorageAccess()`.

Good question. My assumption is that identity is pretty crucial to payment apps so they would all want to use 1P storage, so the proposal above optimizes for that path. But it does seem to be a drawback if there are real payment handlers that want to opt-out of prompting. Maybe we can add an optional `disableRequestStorageAccess` argument to `openWindow()`. I'll keep this in mind when working with initial payment app developers. I think if necessary, it would be possible in the future to flip the default and require developers to call `document.requestStorageAccess()` directly.

> 2. What does blink / chrome plan on doing, since (I don't believe) there are any plans to ship storage access api on chrome?

I don't have the full details on this. Your best bet is probably to ask on https://github.com/whatwg/html/issues/3338. I'll make sure when it's available, Chrome's Payment Handler implementation will hook into that.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-handler/issues/351#issuecomment-566776959