Re: [w3c/payment-request] fix: restore transient activation requirement in show() (PR #1066)

stephenmcgruer left a comment (w3c/payment-request#1066)

Sorry for the delay! Yes, let's draft something up, wdyt of:

```
 <div class="note">
              Redirect flows can cause legitimate loss of transient activation
              before a call to {{PaymentRequest/show()}}. This is a known
              platform-wide problem affecting Payment Request, Digital
              Credentials, WebAuthn, and other APIs that require user
              activation. A general solution is being tracked in <a href=
              "https://github.com/w3c/payment-request/issues/1064">issue
              #1064</a>. Currently, some Chromium-based user agents
              are known to have non-compliant behavior here to allow certain
              calls to Payment Request to not require user activation.
</div>
```

? Happy to iterate. Also curious what @ianbjacobs thinks

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/pull/1066#issuecomment-4379568348
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/payment-request/pull/1066/c4379568348@github.com>