- From: Marcos Cáceres <notifications@github.com>
- Date: Tue, 06 Nov 2018 14:42:06 -0800
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 6 November 2018 22:42:28 UTC
> This prevents me from building a scroll-to-pay flow, which can be very useful for paid web content. Could you help us understand a little bit more what "scroll-to-pay" looks like? > Ask user during Payment Handler registration for permission to allow scroll-to-pay for this handler. They should also be able to change this setting in browser UI. The challenge that we face in browsers is that we rely on HTML's "[triggered by user activation]( https://html.spec.whatwg.org/multipage/interaction.html#triggered-by-user-activation)". The "scroll to pay" case would need to be sufficiently common to warrant having a special code path just to handle this kind of payment interaction. -- 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-request/issues/797#issuecomment-436436098
Received on Tuesday, 6 November 2018 22:42:28 UTC